On Thu, Jun 10, 2021 at 3:13 PM Adam Williamson
<adamwill(a)fedoraproject.org> wrote:
On Thu, 2021-06-10 at 07:38 +0000, Zbigniew Jędrzejewski-Szmek wrote:
> On Thu, Jun 10, 2021 at 05:41:45AM -0000, Luya Tshimbalanga wrote:
> > Hello team,
> >
> > Fedora Design lab maintainer here. I recently replaced GRUB2 by systemd-boot
following this [instruction](https://kowalski7cc.xyz/blog/systemd-boot-fedora-32).
> > I had to remove shim after backing up otherwise secure boot prevent
systemd-boot to execute.
> > The experience is completely refreshing seen the boot screen instead of the
bootloader (activated by holding escape button on a start-up). It will be much better with
secure boot available for.
> > Will it be time to use it on Workstation as alternate bootloader for device
running on EFI? The ideal will be fore Fedora 35 but Fedora 36 may be the fallback.
>
> I think this would be something worth pursing… sd-boot has a smaller
> set of capabilities, but for the cases it covers, it works rather well.
> The scheme is simple, so there is less things to break, and its easy
> to introspect/reconfigure the boot loader from user space (e.g. 'bootctl
list').
The problem with this is that its smaller set of breakage possibilities
just gets added to grub's existing large set of breakage possibilities
to give us a SUPER large set of breakage possibilities. For a
distribution, adding choice can only possibly result in *more*
potential problems (and more engineering work, and more QA time), never
*fewer*. This is the
http://islinuxaboutchoice.com/ problem.
It's only worth adding a choice if that choice makes life so much
better for someone that it's *worth taking on* the additional work. Is
that really the case for a bootloader?
If I were going to advocate for a change, I would:
* Advocate for rEFInd instead of sd-boot or grub2
* Switch to emulated UEFI on BIOS systems
** edk2 provides a fake UEFI implementation for BIOS
Otherwise, it's just not worth it.
--
真実はいつも一つ!/ Always, there's only one truth!