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.
GRUB would still think it boots
Windows directly. (I do not see why it would notice any difference, all that
would change is the name of the image that gets chainloaded.) And systemd-
boot does not need to know that it is being chainloaded from GRUB. So I do
not see why that would not work, without any changes to the software.
--
Chris Murphy