On Wed, May 18, 2022 at 11:21 AM Jiri Konecny jkonecny@redhat.com wrote:
Hi Chris,
honestly, it looks to me like a hack which is required for the cloud images but shouldn't be used out of that. I don't like the solution much, it makes everything much more complicated especially for the "mbr/bios" and similar formats. I'm more inclined for the simplified current solution.
Also I'm thinking if it would be really that helpful. Users usually don't change on the installed system between UEFI and BIOS boot, do they?
Adding bootloader dev for the heads-up about this change and the discussion.
It does happen. Especially if there are problems in one mode vs the other.
But more importantly, this Change is designed as a step toward the eventual removal of grub2-pc as a package. It may be in the future that we'll have OpenCore or some other UEFI emulator for BIOS (similar to what we do for a lot of ARM devices with u-boot), which allows for the shipped GRUB codebase to be drastically simplified to just the stuff for grub2-efi. Having legacy BIOS installs be hybrid BIOS+UEFI would be very useful toward that goal.
I don't particularly want to add too many more partitioning modes. I'm even a bit hesitant to change from inst.mbr to inst.disklabel=(mbr|gpt) because the latter implies permanent support of alternative disklabels. And frankly, I think we want to just get down to GPT (and DASD for s390x) in the far future.