or if you have proxmox 5.3, a good server and (a lot of) patience you can use proxmox for aarch64, or at least i just managed to install centos 7.6 aarch64… a little bit slow but it seems to work
To manage this nethserver-arm-epel with exclusive arch armv7hl is provided. To “fool” yum this package provides “epel-release”. This breaks with the old caution not to imply a official epel-release is available. Opted for this to be compatible with nethserver-release.
Since we shifted to zram, we have a noarch package to set zram-swap up. I wonder if this package could live in the x86_64 too? And with this in all repo’s which would make image creation a bit more straight forward. Not a big deal just a bit cleaner…
EDIT:
If we can agree on the above i would like to ship ownership of the git repository’s to nethserver.
Dec 14 14:54:16 test.local.neth.eu zramstart[4437]: mkswap: only one device argument is currently supported
Dec 14 14:54:16 test.local.neth.eu zramstart[4437]: Usage:
Dec 14 14:54:16 test.local.neth.eu zramstart[4437]: mkswap [options] device [size]
Dec 14 14:54:16 test.local.neth.eu zramstart[4437]: Options:
Dec 14 14:54:16 test.local.neth.eu zramstart[4437]: -c, --check check bad blocks before creating the swap area
Dec 14 14:54:16 test.local.neth.eu zramstart[4437]: -f, --force allow swap size area be larger than device
Dec 14 14:54:16 test.local.neth.eu zramstart[4437]: -p, --pagesize SIZE specify page size in bytes
Dec 14 14:54:16 test.local.neth.eu zramstart[4437]: -L, --label LABEL specify label
Dec 14 14:54:16 test.local.neth.eu zramstart[4437]: -v, --swapversion NUM specify swap-space version number
Dec 14 14:54:16 test.local.neth.eu zramstart[4437]: -U, --uuid UUID specify the uuid to use
Dec 14 14:54:16 test.local.neth.eu zramstart[4437]: -V, --version output version information and exit
Dec 14 14:54:16 test.local.neth.eu zramstart[4437]: -h, --help display this help and exit
Dec 14 14:54:16 test.local.neth.eu zramstart[4437]: swapon: stat failed zramctl:: No such file or directory
Dec 14 14:54:16 test.local.neth.eu zramstart[4437]: swapon: stat failed /dev/zram0:: No such file or directory
Dec 14 14:54:16 test.local.neth.eu zramstart[4437]: swapon: stat failed failed: No such file or directory
Dec 14 14:54:16 test.local.neth.eu zramstart[4437]: swapon: stat failed to: No such file or directory
Dec 14 14:54:16 test.local.neth.eu zramstart[4437]: swapon: stat failed reset:: No such file or directory
Dec 14 14:54:16 test.local.neth.eu zramstart[4437]: swapon: stat failed Device: No such file or directory
Dec 14 14:54:16 test.local.neth.eu zramstart[4437]: swapon: stat failed or: No such file or directory
Dec 14 14:54:16 test.local.neth.eu zramstart[4437]: swapon: stat failed resource: No such file or directory
Dec 14 14:54:16 test.local.neth.eu zramstart[4437]: swapon: stat failed busy: No such file or directory
OOPS…, maybe i did over see something
We running a quite old kernel on centos (3.10.xx) which may not provide multithreading for zram…will investigate too!
Actually i did doubt very long to use lz4 on arm because of the not fully optimized SIMD instruction-set. But after reading concluded it should be in-par with x86_64 by now… so i went for it as lz4 outperforms lzo…