As I've said in another topic, I've migrated to 66 from runit. I had a setup consisting of a /dev/zram0 and a swapfile.
With these config files, I had zram and the swapfile working on boot:
# /etc/modules-load.d/zram.conf
zram
# /etc/udev/rules.d/99-zram.rules
KERNEL=="zram0", ATTR{disksize}="3G" RUN="/usr/bin/mkswap /dev/zram0", TAG+="systemd"
# relevant lines in /etc/fstab
/dev/zram0 none swap defaults,pri=0 0 0
/swapfile none swap defaults,pri=0 0 0
After the suite66 migration, though, the zram module isn't loaded automatically, and the swapfiles seem to be ignored. I have to type this in a root shell:
modprobe zram && swapon /dev/zram0 -p 20 && swapon /swapfile -p 0
Output of
mount -av:
/ : ignored
/home : already mounted
none : ignored
none : ignored
/tmp : already mounted
I figured out the "zram not automatically loading" part. The /etc/66/script/modules.sh didn't like the fact that the file had no terminating newline. Still need to figure out why mount ignores my swaps.
What does your 66 config look like? /etc/66/service/boot@
https://paste.artixlinux.org/view/070ec392
Apparently there's a
SWAP= key I missed when setting up
66-env. D'oh. Will try setting it to yes and checking the results.
EDIT:
66-env -t boot -e vim boot@system && 66-enable -F -t boot boot@system
and setting SWAP to !yes solved the problem. Should've read the config file more carefully.
BTW I've updated suite66-scripts in testing and used s6's script for module-load, in hope to avoid a possible issue like you had.
The new script in gremlins/suite66-scripts indeed fixes the problem (tested removing the trailing newline in zram.conf and rebooting). Thanks!
@capezotte Take a look at zramen (https://github.com/atweiden/zramen) for zram configuration - it is very nice ;)
Which is also in Universe, both zramen and it's service file