Updating the kernel on an encrypted lvm install
Hi there,
I am running Slackware64 14 with encrypted lvm. The kernel I am using is 3.2.29 and it looks like the kernel was updated to 3.2.45. Since I want my system to stay somewhat up to date on patches I figured I should upgrade the kernel, but I am unsure of the process to make sure my encrypted lvm will boot afterwards. Could someone point me to a guide for such a scenario? |
Install the new kernel-generic plus the kernel-modules packages (and kernel-headers and kernel-sources if you ever want to compile something that needs kernel sources/headers) using installpkg (do not use upgradepkg - you will want to keep your working configuration until you are sure that you can boot the new kernel).
After installing the kernel and its modules, run Code:
/usr/share/mkinitrd/mkinitrd_command_generator.sh Then you add a new definition to /etc/lilo.conf for the new kernel & initrd and run lilo to make it stick. An example of how this is most easily done for the 3.2.45 kernel of Slackware64 without overwriting any existing initrd file (run the three commands as root... and yes, that "$( xxxxxx)" is a real full commandline, which will execute the mkinitrd command immediately instead of merely showing it as an on-screen example): Code:
$( /usr/share/mkinitrd/mkinitrd_command_generator.sh -k 3.2.45 -a "-o /boot/initrd_3.2.45.gz" ) Eric |
Thank you for the very detailed response!
|
All times are GMT -5. The time now is 06:36 AM. |