On Thursday, 25 June 2026 10:19:49 IDT Vitaly Zaitsev via devel wrote: > On 25/06/2026 08:59, Gerd Hoffmann wrote: > > There are reasons why this is model is not used any more and > > why UEFI firmware is able to read FAT filesystems. > > UEFI firmware can read any file system for which it has drivers. Fedora > simply needs to sign the efifs package with the Fedora Secure Boot key. > > systemd-boot supports efifs by default. Users just need to copy the > required driver to the EFI/systemd/drivers/ directory.
Reading this thread shows interesting dilemma between different approaches: * Restrict everything to FAT and get more limited but simpler boot chain * Allow kernel+initrd in "real" filesystem, but use some "bridge" (GRUB file systems, EFI drivers, ...) with maintenance issues. I don't see a clear "winner" strategy, so I'll bite and try to add another kind of "bridge" for file system access. (you are welcome to hit me hard if I'm proposing some total BS) What if the boot sequence would be: EFI -> "bootstrap" UKI on FAT -> load and "kexec" real kernel from "/boot" (not necessarily FAT) So the "bootstrap" kernel is used as an intermediate boot loader: * It should have all needed FS drivers built in (but no quality/maintenance issues like GRUB) * I'm not sure it really work (e.g: can the initramfs under /boot be loaded/executed?) * Even if it does, I'm not sure about the gain -- would the "bootstrap" kernel be minimal and constant enough so we can consider it as "filesystem-access shim" ? Just food for thought... -- Oron Peled Voice: +972-4-8228492 -- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
