Hi Adam,
Thanks very much for this. Your continued enthusiasm for keeping us
informed in such clear detail is hugely appreciated. And your thoughts
on the F18 draft of the Installation Guide when it eventuates will be
extremely welcome if your schedule permits. :)
Incorporating these points into the Installation Guide won't be a
problem. I'll clarify what bootloader options we now provide. How can we
expect UEFI to differ though, and will this need to be documented?
Also, I tried to unset my drive for receiving a bootloader but had no
luck. Maybe this is because I can only muster one drive in my VM and the
button in the instructions you quoted isn't displayed in such a case.
But if the button in question is the 'Set as Boot Device' button, then
it's not working for me as it should. The tick that marks the drive as
the boot device remains.
Let me know if that's bug-worthy. In the meantime, I'll document the rest.
Thanks again!
Jack
On 12/01/2012 08:19 AM, Adam Williamson wrote:
Hey, folks (Jack especially). I have it on my (very long) todo list to
look through the changes to the installation guide and see if I can
contribute anything, but we were talking about this in #anaconda this
morning and I thought I'd outline it for the install guide before I
forget the plan again. Handling of bootloader install is somewhat
different in newUI. This is all about BIOS - UEFI is completely
different.
So what newUI is capable of is either installing the bootloader to a
partition MBR, or not installing the bootloader at all. Currently there
is no option to install bootloader to a partition, which was possible in
oldUI. Installing the bootloader to a partition is done only by those
who multiboot various OSes using a 'chainload' system - they have a
bootloader in the MBR which 'chainloads' bootloaders for each of their
OSes, each of which resides in the / or /boot partition for that OS.
The plan is for those who have such setups to just not install a
bootloader at all, and then do their bootloader configuration manually
post-install. Anyone who for some reason doesn't want a bootloader
installed to an MBR gets to do their own configuration.
In the UI you are able to specify which disk the bootloader should be
installed to (or that it shouldn't be installed at all). You do this on
the 'disk selection' screen - the first screen you see after clicking on
the 'Installation Destination' spoke. You have to click on 'Full disk
summary and options...' and you get a dialog that lets you pick the
target disk for the bootloader. To set it to not install a bootloader at
all, right now, this is the procedure:
"highlight whatever disk has the bootloader check, click the button, and
it'll unset that device for receiving the bootloader. Thus, you should
not get a bootloader installed."
clumens notes that this isn't the best UI, but changing it would break
string freeze. See https://bugzilla.redhat.com/show_bug.cgi?id=867469
for details.
If you do not select a target disk, anaconda will default to installing
the bootloader to the MBR of the first disk (of those selected as
'install target disks' on the picker screen) that appears to be a viable
target, in enumeration order (so it'll try sda, then sdb, then sdc, and
so on, and the first one which passes the 'bootloader target' tests gets
the bootloader). This part is unchanged from F17.
Hope that's useful! Thanks.
--
Jack Reed
Content Author
Engineering Content Services
Red Hat Asia Pacific
Brisbane, Australia
Phone: +617 3514 8184
--
docs mailing list
docs@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/docs
