On Tue, Jul 26, 2022 at 1:43 PM Kevin Kofler via devel
<devel(a)lists.fedoraproject.org> 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.
--
真実はいつも一つ!/ Always, there's only one truth!