On Sun, Jan 23, 2022 at 1:50 PM Neal Gompa <ngompa13@xxxxxxxxx> wrote: > > On Sun, Jan 23, 2022 at 6:54 AM Peter Robinson <pbrobinson@xxxxxxxxx> wrote: > > > > On Sun, Jan 23, 2022 at 2:37 AM Neal Gompa <ngompa13@xxxxxxxxx> wrote: > > > > > > On Sat, Jan 22, 2022 at 5:21 PM Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote: > > > > > > > > https://fedoraproject.org/wiki/Fedora_35_Final_Release_Criteria#Bootloader_disk_selection > > > > > > > > "The installer must allow the user to choose which disk the system > > > > bootloader will be installed to, and to choose not to install one at > > > > all. " > > > > > > > > The "choose not to install one at all" doesn't really apply to UEFI. I > > > > wonder if we can just drop the whole criterion? (I'm still hopeful > > > > that one day the entirety of bootloader UI in the installer goes > > > > away.) > > > > > > > > So what you get is a system without an EFI system partition (or an > > > > existing ESP that isn't used), but all the bootloader stuff is put on > > > > the /boot volume. So it's not going to boot, which makes the > > > > installer's warnings true. The one thing *not* copied for some reason > > > > is the stub grub.cfg. But shim, grub, the real grub.cfg, and BLS > > > > snippets are all there - just on ext4 /boot which the firmware can't > > > > read so the system doesn't boot. It's harmless because the user signed > > > > up for this after all, but it's also kinda pointless. > > > > > > > > > > > > Reproduce steps: > > > > 1. Any that use Anaconda, from any release, but I just used this: > > > > Fedora-Workstation-Live-x86_64-Rawhide-20220119.n.0.iso > > > > 2. Boot it, launch installer > > > > 3. Installation destination keep all defaults > > > > 4. Click blue text at the bottom "Full disk summary and boot loader..." > > > > 5. Select the (in my case single) drive, click the "Do not install > > > > bootloader" button > > > > 6. Close and install > > > > > > > > > > The ability to not install the bootloader is used for creating some of > > > the images. And it's also useful in advanced installations where > > > people are using custom boot managers. > > > > Which images? > > Hmm, now that I look, I guess we're not doing it anymore for the ARM > ones. But I think we'll be using that for the RISC-V ones once that > gets brought into Fedora. Nope, RISC-V will be handled like arm and use UEFI/grub2 so there should be no need there either. _______________________________________________ Anaconda-devel mailing list -- anaconda-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to anaconda-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/anaconda-devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
