Re: F37 Change: Deprecate Legacy BIOS (System-Wide Change proposal)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Apr 7, 2022 at 7:10 PM Demi Marie Obenour <demiobenour@xxxxxxxxx> wrote:
>
> On 4/7/22 15:30, Chris Murphy wrote:
> > On Thu, Apr 7, 2022 at 12:20 AM Gerd Hoffmann <kraxel@xxxxxxxxxx> wrote:
> >>
> >>   Hi,
> >>
> >>> On the cloud side, it's been very difficult to articulate any benefits
> >>> for supporting UEFI when the majority of the consumers of Fedora Cloud
> >>> don't have any pressing need to do it and things like hibernation and
> >>> snapshotting are non-functional. Last year, I changed Fedora Cloud to
> >>> hybrid boot[6] so that our image artifacts support both boot modes.
> >>
> >> Any chance for regular anaconda installs doing a hybrid boot setup too?
> >
> > Anaconda is used for this purpose to make dual firmware supporting VM
> > images. Cloud edition does it, and it's also done within RHEL and
> > CentOS.
> >
> > I would sooner expect optical boot support to go away before BIOS
> > boot. But I only have anecdotes to go on.
> >
> >>
> >> The installed systems will look pretty much the same (gpt with both
> >> bios-boot and efi-esp partition) no matter how they where installed,
> >> and it'll be trivial to switch from BIOS to UEFI without reinstalling
> >> the system.
> >>
> >> We can fade out some stuff already (mbr support), and painless switching
> >> to UEFI for systems which where installed in BIOS mode for whatever
> >> reason should also help UEFI adaption.
> >
> > There have been two prior attempts to move to GPT by default (i.e.
> > drop MBR by default when legacy BIOS is detected), and due to firmware
> > bugs, it never progressed to any Fedora release. I can't guess what
> > percent of hardware in the Fedora community is BIOS vs UEFI, and it's
> > even harder to estimate what percent of BIOS hardware are affected by
> > the GPT bug.
>
> Can the disk be partitioned so that it is valid for *both* MBR and GPT?
>

There are two options here: protective MBR and hybrid MBR.

Protective MBRs are well-supported and I believe created by default
when you create a GPT partitioning scheme for BIOS systems already
with Anaconda. I think it's done with UEFI as well, but if not, we can
certainly force it.

The second option is known as hybrid MBR. The gdisk utility can create
them: https://www.rodsbooks.com/gdisk/hybrid.html

Needless to say, it's... interesting... I'm not sure if more tools
support hybrid MBRs since this was last refreshed in 2019.

It's also kinda scary and not really necessary unless you need to
interoperate with OSes that expect MBR in a mixed BIOS+UEFI boot
setup.






--
真実はいつも一つ!/ Always, there's only one truth!
_______________________________________________
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




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux