Welcome to Eric Hameleers (Alien BOB)'s Wiki pages.
This is an old revision of the document!
Installation to encrypted partitions works well with the stock Slackware kernels.
If you want to compile your own custom kernel to work with LUKS encrypted partitions you need to enable at least the following two options in your kernel configuration:
Multiple devices driver support (RAID and LVM) ---> <*> Device mapper support <*> Crypt target support
This is equivalent to the following options in your
Do not compile these as module! They are required in your kernel.
I'd like to correct two things omitted in the README_CRYPT.TXT file for Slackware 12.0. They relate to setting up an encrypted root partition in Slackware.
- First issue:
When you finish the installation and the README prompts you to
perform a chroot into the new installation, there is one command missing. As a result, there will not be a
/dev/mapper/cryptrootavailable inside the chroot and therefore the attempt to install LILO will fail.
Please change the list of commands that goes like
mount -o bind /proc /mnt/proc mount -o bind /sys /mnt/sys chroot /mnt
mount -o bind /proc /mnt/proc mount -o bind /sys /mnt/sys mount -o bind /dev /mnt/dev chroot /mnt
and then proceed with the remainder of the README.
IF for whatever reason you get something like this error after running ”
mount -o bind /dev/mnt/dev”:
mount: wrong fs type, bad option, bad superblock on /dev, missing codepage or other error In some cases useful info is found in syslog - try dmesg | tail
then please run this command instead:
cp -a /dev/mapper /mnt/dev/
which will add the required files intto the installed system so that lilo will install successfully. I have had reports from several people who experienced the above error, and I have seen it happen myself too, for reasons unclear to me.
When the README mentions ''Change the boot device to name of the small unencrypted partition you've created and which is mounted under /boot'.' it must be clear that this action should not be taken when you install LILO to the MBR. The example in the README is meant for a Slackware setup where there is another OS bootloader (such as MS Windows) already installed in the MBR, and your Slackware installation is a secondary install for which LILO needs to install itself into the root sector of a partition instead.
I hope this clarifies the issues some people reported to me after Slackware 12.0 was released.
– Eric 03-july-2007