"IT3 Stuart Blake Tener, USNR-R" wrote: > While having a 15k initrd.gz in memory doesn't bother me a bit, I was of > the understanding that there was a new way (root pivot, or chroot, I am by > no means an expert in that area) to effectively "pull the rug out from under > roots feet", and switch to a new root, thus displacing the olde one into > oblivion. Is this an accurate estimation of the technologies, which are now > existent with respect to this issue? Loop-AES' build-initrd.sh supports both old change_root and new pivot_root methods of changing to encrypted root. Reason why old initrd can't be unmounted in both cases is that a device (the encrypted root) on it has been losetup'ed and is busy until that device is un-losetup'ed. Regards, Jari Ruusu <jari.ruusu@xxxxxxxxxx> - Linux-crypto: cryptography in and on the Linux system Archive: http://mail.nl.linux.org/linux-crypto/
