I have my swap encrypted using dm-crypt which works fine but the recent reorganisation of the initscripts relating to dm-crypt and swap initialisation has brought about an error message that /dev/mapper/crypt-swap can't be stat'd. I suspect this is because my /etc/fstab entry for swap is processed by a swapon -a by the initial swap activation logic but encrypted swap isn't initialised until later in the additional swap activation. If this is the case, is there any reason why encrypted swap activation can't be done at initial swap activation time? This wasn't a problem under baselayout-1.1.11 but seems to have been introduced at baselayout-1.11.12. /etc/fstab swap entry: /dev/mapper/crypt-swap none swap sw 0 0 /etc/conf.d/cryptfs entry: swap=crypt-swap source='/dev/md/6' Regards, Neil Darlow Reproducible: Always Steps to Reproduce: 1. 2. 3.
has nothing to do with recent reorganization ... the error has always been occuring on your box, the difference is that i removed the >&/dev/null from the swapon -a command in /sbin/rc ive fixed it in cvs such that: - very first swapon is sent to /dev/null - the second swapon is NOT sent to /dev/null since everything should be setup by that point
