Chris Murphy wrote:
> A work around is having GRUB set an NVRAM variable indicating the next
> boot should be Windows. That's an instruction to the firmware, so
> there's no intermediary, thus measured boot works. The next boot (from
> Windows) would boot Fedora again. GRUB can't get or set EFI variables
> yet. systemd-boot, meanwhile, will be supporting BootNext in their
> next release.
So, can we not, in GRUB, instead of chainloading the Windows bootloader,
chainload a systemd-boot copy preconfigured to BootNext to Windows?
Kevin Kofler
_______________________________________________
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
