4 ms·
README_CRYPT.TXT in the root of the distribution[0] describes how to do this, step by step, including the relevant theory so you know what you're doing. After
by cuckcuckspruce 11y ago
README_CRYPT.TXT in the root of the distribution[0] describes how to do this, step by step, including the relevant theory so you know what you're doing. After all of that it shows you the /usr/share/mkinitrd/mkinitrd_command_generator.sh command which you can use to generate the command that you need to build the initrd. Quoting from the docs:
The mkinitrd package in Slackware 14.0 (and on) ships with a script called
'mkinitrd_command_generator.sh'. If you run this script, it will analyze
your Slackware configuration and make a smart suggestion about the 'mkinitrd'
command you have to type in order to create an initrd.gz with all the bells
& whistles. The script will recognize your kernel version, root partition
and filesystem, it will find out if you are using LUKS and/or LVM and will
determine what kernel modules your initrd needs to mount the root filesystem.
The following command will save you the headache of figuring this out all
by yourself:
# /usr/share/mkinitrd/mkinitrd_command_generator.sh -r
It should emit a string like this (your system will probably give different
parameter values):
mkinitrd -c -k 3.14.10-smp -m ext3 -f ext3 -r /dev/cryptvg/root -C /dev/sdx2 -L
The administrator of that machine can examine the output of that command and determine if it is correct after reading the theory about how the initrd needs to be built. If it is, it's a simple one liner, but if not, it's simple enough to either write a wrapper script or copy the script to /usr/local/sbin/mkinitrd_command_generator.sh and make the necessary changes.
[0] ftp://ftp.slackware.com/pub/slackware/slackware64-current/README_CRYPT.TXT