mkinitrd output could use an update in messaging, beyond the mention of lilo...

slvr32 · 05-29-2021, 01:20 PM

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/Slackware

On 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...

bassmadrigal · 05-30-2021, 11:25 AM

Slackware does still default to using lilo and users need to go above and beyond to be able to install with UEFI (thus allowing elilo) or switching to grub/syslinux/rEFInd after setup finishes. I think anyone who sees that message will understand the meaning behind it and will know they may need to update their bootloader.

That being said, it Pat wanted to update it, he could change it to something like: "Be sure to update your bootloader if it needs it."

dodoLQ · 05-30-2021, 11:46 AM

And why not updating setup with a specific elilo entry? There's no choice of elilo actually.

bassmadrigal · 05-30-2021, 12:01 PM

Quote:

Originally Posted by dodoLQ

And why not updating setup with a specific elilo entry? There's no choice of elilo actually.

The Slackware setup will prompt you to use elilo if, and only if, you boot the install media as UEFI. If you boot the install media using legacy or compatibility boot (emulating the older BIOS instead of the newer UEFI), setup can't set up elilo. This is because efibootmgr requires the /sys/firmware/efi/ folder, which is only generated when booting via UEFI. If that folder doesn't exist, efibootmgr can't update the UEFI firmware to know of elilo, which means you can't boot without using the horrible EFI shell.

dodoLQ · 05-30-2021, 12:17 PM

Humm.. Ok, 'ill check that when burning and running the official Slack-15.0_ISO file on my core i5 system (with UEFI boot activated in the bios of course)

Thanks!

slvr32 · 05-30-2021, 12:35 PM

Quote:

Originally Posted by bassmadrigal

Slackware does still default to using lilo and users need to go above and beyond to be able to install with UEFI (thus allowing elilo) or switching to grub/syslinux/rEFInd after setup finishes.

I don't know if you've done a fresh install of x86_64-current on a UEFI machine lately, but there's a really straightforward set of prompts that essentially make installing ELILO an easy/automated process during setup, more or less equivalent to installing LILO on a non-UEFI machine.

bassmadrigal · 05-31-2021, 03:14 PM

Quote:

Originally Posted by slvr32

I don't know if you've done a fresh install of x86_64-current on a UEFI machine lately, but there's a really straightforward set of prompts that essentially make installing ELILO an easy/automated process during setup, more or less equivalent to installing LILO on a non-UEFI machine.

It's the same with the 14.2 installer. The installer still defaults to lilo, but if it detects UEFI booting, it will prompt to skip lilo and set up elilo. Since it asks if you want to skip lilo, I lumped it into the "above and beyond" category (although, much easier than grub or other bootloaders as it is still able to be accomplished during the install).