Add rock64 specific overlaygit status

This commit is contained in:
Taylor Helsper 2019-10-09 07:54:16 -05:00
parent 4fce38cc9f
commit 713521fcc2
3 changed files with 47 additions and 0 deletions

View File

@ -10,6 +10,7 @@ mkdir -p out/rootfs_debian/
### Make rock64 rootfs ###
cp -rf rootfs/standard/* out/rootfs_rock64/
cp -rf rootfs/rock64/* out/rootfs_rock64/
cp -f CHANGELOG out/rootfs_rock64/usr/share/mynode/changelog
rm -f out/mynode_rootfs_rock64.tar.gz
tar -zcvf out/mynode_rootfs_rock64.tar.gz ./out/rootfs_rock64/*

View File

@ -0,0 +1,12 @@
# configuration values for the armbian-ram-logging service
#
# enable the armbian-ram-logging service?
ENABLED=true
#
# size of the tmpfs mount -- please keep in mind to adjust /etc/default/armbian-zram-config too when increasing
SIZE=100M
#
# use rsync instead of cp -r
# requires rsync installed, may provide better performance
# due to copying only new and changed files
USE_RSYNC=false

View File

@ -0,0 +1,34 @@
# configuration values for the armbian-zram-config service
#
# enable the armbian-zram-config service?
#ENABLED=true
# percentage of zram used as swap compared to physically available DRAM.
# Huge overcommitment (300) is possible and sometimes desirable. See
# https://forum.armbian.com/topic/5565-zram-vs-swap/?do=findComment&comment=61082
# and don't forget to adjust $MEM_LIMIT_PERCENTAGE below too.
# ZRAM_PERCENTAGE=50
# percentage of DRAM available to zram. If this amount is exceeded the zram
# devices used for swap simply behave as if the device is full. You need to
# adjust/increase this value only if you want to work with massive memory
# overcommitment (ZRAM_PERCENTAGE exceeding 150 for example)
# MEM_LIMIT_PERCENTAGE=50
# create how many zram devices max for swap
# ZRAM_MAX_DEVICES=4
# Which algorithm for zram based swapping. Seems lzo is best choice on ARM:
# https://forum.armbian.com/topic/8161-swap-on-sbc/?do=findComment&comment=61668
# SWAP_ALGORITHM=lzo
# Which algorithm to choose for zram based ramlog partition
# RAMLOG_ALGORITHM=zstd
# Which algorithm to choose for zram based /tmp
# TMP_ALGORITHM=zstd
# If defined a separate partition will be used as zram backing device. Be CAREFUL
# which partition you assign and read starting from CONFIG_ZRAM_WRITEBACK in
# https://www.kernel.org/doc/Documentation/blockdev/zram.txt
# ZRAM_BACKING_DEV=/dev/nvme0n2