mkinitrd output could use an update in messaging, beyond the mention of lilo...
by slvr32 from LinuxQuestions.org on (#5JE4X)
I'm not sure what the messaging could be changed to, but the mention of lilo is outdated for some...
Code:/boot
# mkinitrd -c -k 5.10.41
48147 blocks
/boot/initrd.gz created.
Be sure to run lilo again if you use it.I happen to use lilo or elilo on my own boxes, but some probably like grub, etc...
In the case above, after a kernel upgrade, on a box with UEFI, I happen to also do the following, just for other considerations in updated messaging...
Code:/boot
# cp vmlinuz initrd.gz /boot/efi/EFI/SlackwareOn the other hand, maybe the use of mkinitrd implies that someone has also looked at other related hints about initrd, using various boot managers, etc...
Code:/boot
# mkinitrd -c -k 5.10.41
48147 blocks
/boot/initrd.gz created.
Be sure to run lilo again if you use it.I happen to use lilo or elilo on my own boxes, but some probably like grub, etc...
In the case above, after a kernel upgrade, on a box with UEFI, I happen to also do the following, just for other considerations in updated messaging...
Code:/boot
# cp vmlinuz initrd.gz /boot/efi/EFI/SlackwareOn the other hand, maybe the use of mkinitrd implies that someone has also looked at other related hints about initrd, using various boot managers, etc...