Hi, > > So I can't say I'm thrilled about a future that depends on EFI for > > virt, but I'm resigned to the fact this is the direction the world > > is taking. So we're not likely to have any choice and will have to > > work to mitigate any downsides it brings. > > Right. > > Preferably the installer should detect and setup the system either with > sd-boot ( if setting equals UEFI ) or grub ( if setting not equals UEFI ) I have my doubts that building on sd-boot and drop grub2 is going to fly. One problem with sd-boot is that the kernels must stay on the ESP, which can be a problem for dual-boot installs (where Fedora has to run with the existing ESP and can't just create one which is big enouth). Another problem is that grub2 covers more architectures than sd-boot. What is the plan for armhfp, ppc64, s390x? IMHO a better preparation for deprecating BIOS would be to make new installs bootable with both BIOS and UEFI. Which isn't hard at least for the "[x] use all space" case where Fedora can partition the disk as it pleases: Use gpt. Create a bios boot partition, install grun-pc there. Create a ESP partition, install grub-efi there. Create a partition for the /boot filesystem. Have both grubs pick up BLS config from /boot/loader. take care, Gerd _______________________________________________ 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
