On Thu, Jan 6, 2022 at 11:46 AM Fabio Valentini <decathorpe(a)gmail.com> wrote:
I seem to remember that /boot/efi/loader and /boot/efi/$machine-id
folders were used for gummiboot / early systemd-boot file snippets.
Back in those days, bootloader config file snippets for new kernels
were only created for those bootloaders if those directories existed,
IIRC.
Yes. It's a bit of a saga.
Fedora takes an al la carte approach to the Boot Loader Spec, where we
effectively have two $BOOT volumes. One for the bootloader and a
forwarding configuration file, a second for the rest of the
configuration files plus kernel and initramfs.
Boot Loader Spec defines only one $BOOT where everything goes:
bootloader, configs, kernel, initramfs.
I suppose the main rationale for the approach we took is the path of
least change. The main change was getting away from constant grub.cfg
modification, and using drop-in configuration files that ostensibly
any bootloader could support. But we didn't commit to the bigger
changes: discovery by partition type code/UUID instead of filesystem
UUID baked into a configuration file which has to be searched for by
the bootloader; and the idea of putting kernel/initramfs on FAT was
never popular.
Possibly a big step toward better BLS compliance that also wouldn't be
too controversial:
* use XBOOTLDR partition type code for our ext4 /boot, and discover it
by that type code rather than than by fs UUID
* mount XBOOTLDR at /boot
* mount EFI System at /efi
But now I'm in the weeds, and it should be a different thread to
discuss doing something different.
--
Chris Murphy