4 ms·
>Grub 2 is complex to configure, but there are other bootloaders that are much easier to configure, e.g. syslinux. ~~Yes but syslinux is bios-only. So if you h
by faho 4y ago
>Grub 2 is complex to configure, but there are other bootloaders that are much easier to configure, e.g. syslinux.
~~Yes but syslinux is bios-only. So if you have to support EFI too (and you do because there's EFI-only hardware), you now either need to support syslinux and an EFI bootloader, or a bootloader that supports both like Grub 2.~~
Edit: The article seems to suggest that syslinux can be removed if bios boot is no longer supported. I read that as it being bios-only, but it seems to support EFI?
>Restricting the boot method to EFI does not reduce the need for documentation in any way.
You still need documentation, yes. But you no longer need any documentation for booting with BIOS.
You no longer need to say "X is only supported in EFI, if you boot via BIOS you need to do Y" or anything like that, and keep those parts updated.
The part of the docs that says "To boot EFI, do X. To boot BIOS, do Y" can be cut down to "To boot Fedora, ensure X".
That is a reduction in the amount of documentation.
- usrn 4y agoYou arguably don't need a bootloader at all with EFI. You could just use the efistub.
- adrian_b 4y agoYes, it is easy to make a bootable device that can use either syslinux to boot when legacy BIOS is used or efistub to boot when EFI booting is used, eventually loading the same kernel. No other bootloader is needed.
- imtringued 4y agoOr systemd-boot. I will admit I am using Grub2 on my current Linux installation but I never liked grub. I think grub sucks.