On Tue, Jul 26, 2022, at 4:59 PM, Neal Gompa wrote: > On Tue, Jul 26, 2022 at 1:43 PM Kevin Kofler via devel > <devel@xxxxxxxxxxxxxxxxxxxxxxx> wrote: >> >> Chris Murphy wrote: >> > On Tue, Jul 26, 2022, at 4:06 PM, Kevin Kofler via devel wrote: >> >> As I already mentioned the last time this has come up: Why can we not, >> >> instead of chainloading Windows directly, chainload a systemd-boot >> >> configured to always bootnext to Windows? >> > >> > Pretty sure shim still hard codes the name grub$arch.efi as the 2nd >> > bootloader. Hence having to rename sd-boot as grubx64.efi for shim to find >> > and run it. They can't co-exist right now. Also, there's no current plan >> > by anyone to add systemd-boot for Secure Boot signing. >> >> That is not what I suggested. >> >> I suggested shim → GRUB → systemd-boot → Windows (and shim → GRUB → Fedora, >> systemd-boot would be configured to always reboot to Windows, booting Fedora >> from GRUB would bypass it entirely), not shim → systemd-boot → Windows. >> > > That may work indeed, but we'd need to ensure it can't be used as a > stage-two bootloader somehow. Maybe systemd-boot signed with a Fedora key only GRUB provides, and shim does not? Either shim or GRUB must have this key so regardless we need help from folks who can sign Fedora's bootloaders. Seems more complicated compared to a user space program that merely does `efibootmgr --bootnext $windows` -- Chris Murphy _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx 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/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
