https://fedoraproject.org/wiki/Fedora_35_Final_Release_Criteria#Bootloader_d...
"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
-- Chris Murphy
On Sat, Jan 22, 2022 at 5:21 PM Chris Murphy lists@colorremedies.com wrote:
https://fedoraproject.org/wiki/Fedora_35_Final_Release_Criteria#Bootloader_d...
"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:
- 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.
-- 真実はいつも一つ！/ Always, there's only one truth!
On Sun, Jan 23, 2022 at 2:37 AM Neal Gompa ngompa13@gmail.com wrote:
On Sat, Jan 22, 2022 at 5:21 PM Chris Murphy lists@colorremedies.com wrote:
https://fedoraproject.org/wiki/Fedora_35_Final_Release_Criteria#Bootloader_d...
"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:
- 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?
On Sun, Jan 23, 2022 at 6:54 AM Peter Robinson pbrobinson@gmail.com wrote:
On Sun, Jan 23, 2022 at 2:37 AM Neal Gompa ngompa13@gmail.com wrote:
On Sat, Jan 22, 2022 at 5:21 PM Chris Murphy lists@colorremedies.com wrote:
https://fedoraproject.org/wiki/Fedora_35_Final_Release_Criteria#Bootloader_d...
"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:
- 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.
-- 真実はいつも一つ！/ Always, there's only one truth!
On Sun, Jan 23, 2022 at 1:50 PM Neal Gompa ngompa13@gmail.com wrote:
On Sun, Jan 23, 2022 at 6:54 AM Peter Robinson pbrobinson@gmail.com wrote:
On Sun, Jan 23, 2022 at 2:37 AM Neal Gompa ngompa13@gmail.com wrote:
On Sat, Jan 22, 2022 at 5:21 PM Chris Murphy lists@colorremedies.com wrote:
https://fedoraproject.org/wiki/Fedora_35_Final_Release_Criteria#Bootloader_d...
"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:
- 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.
On Sun, Jan 23, 2022 at 11:53:37AM +0000, Peter Robinson wrote:
On Sun, Jan 23, 2022 at 2:37 AM Neal Gompa ngompa13@gmail.com wrote:
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?
Looking at fedora-kickstarts the fedora-container-common.ks has it disabled. And in my example for lmc live iso it is set to none.
Brian
On Sat, 2022-01-22 at 15:20 -0700, Chris Murphy wrote:
https://fedoraproject.org/wiki/Fedora_35_Final_Release_Criteria#Bootloader_d...
"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.)
We (re-)added the capability and the criterion because it was heavily requested. anaconda 'new UI' didn't let you do this for a while, and a lot of people complained. It is intended for people who maintain their own custom multi-OS bootloader config and do not want the OS to mess with it.
I'm not sure if what it does for UEFI installs is intentional or has really been thought about, so there could be scope for changing that, and clarifying the release criteria expectations about it. But both the behaviour and the desire for it were fairly clearly established for BIOS installs.
anaconda-devel@lists.stg.fedoraproject.org
-
Adam Williamson -
Brian C. Lane -
Chris Murphy -
Neal Gompa -
Peter Robinson