On Fri, Jul 29, 2022, at 4:38 AM, Kamil Paral wrote:
>> - Documentation: GRUB's Windows boot option may not work, how to use
>> efibootmgr --bootnext and --bootorder
>
> Currently there is this (insufficient, of course):
> https://ask.fedoraproject.org/t/windows-with-encrypted-disks-bitlocker-cant-be-booted-from-the-grub-boot-menu/20612
Looks pretty good actually. What's missing or unclear?
I think we should consider swapping the built-in bootmanager and efibootmgr
sections. The efibootmgr section needs enhancement first: how to find the
Windows boot entry number; use case 1: do a one time boot of windows with
--bootnext; use case 2: persistently make Windows or Fedora the default boot OS
with --bootorder; use case 3: boot Fedora from Windows when Windows is the
default boot OS. Each with examples and screenshots.
The efibootmgr CLI is a consistent interface for everyone. It's much easier to
document concisely. The firmware method defies screenshots or examples. I'd
either make it a secondary section or remove it, but have no strong feeling
about it.
>
> I'd like to see some proper guide available in Fedora Docs/Quick Docs/wiki
> that I could reference from that Common Issue entry.
I'd like Ask and Quickdoc to be essentially identical. This no conflicting info
between them. Each is a single authoritative source. And each should be updated
in parity.
>> In the near term, we're looking at an awareness and documentation effort,
>> while seeing how the other options shake out. And it probably doesn't
>> significantly matter whether we change the release criterion now or also
>> wait a bit longer.
>
> We can change the criterion shortly before Final, if needed. Since we expect
> the situation to improve in the future, we could just add a (temporary)
> footnote to the existing criterion saying that the special case of Windows
> partitions encrypted by Bitlocker are exempt from the requirement (of booting
> Windows from GRUB).
>
One pretty big weakness I missed in the summary: the non-functional Windows
menu item in GRUB. That's quite a trap. I'm not sure any documentation
adequately addresses this. But I also don't know an easy way to detect this
situation and either inhibit creation of or remove this item.
--
Chris Murphy
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
