On Tue, Sep 20, 2022, at 9:50 AM, Brian C. Lane wrote: > On Mon, Sep 19, 2022 at 12:16:33PM -0700, Adam Williamson wrote: >> "The installer must be able to install into free space alongside an >> existing clean Windows installation and install a bootloader which can >> boot into both Windows and Fedora." >> >> to say: >> >> "The installer must be able to install into free space alongside an >> existing clean Windows installation. As long as the Windows >> installation does not have BitLocker enabled, the installer must also >> install a bootloader which can boot into both Windows and Fedora." > > We have reached a point where boot security is important enough that > Windows is now only allowing their bootloader to be used. With bitlocker > enabled this is working exactly how it was designed so I'd change the > wording to require that grub2 doesn't prevent windows from continuing to > boot via their preferred method and leave it at that. > > And while there may be a possible solution using BootNext, until someone > does the work and tests it there is no point in requiring grub2 to do > something it cannot do. An additional topic is having boot entries for Windows (and macOS) that don't work in the meantime. While we could just remove the scripts that create these entries to chainload another bootloader, they're still needed for BIOS systems which don't support bootnext. -- 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, report it: https://pagure.io/fedora-infrastructure/new_issue
