On Thu, 2014-01-09 at 15:36 -0500, Gene Czarcinski wrote: > OK, here are some additional thoughts/considerations ... > > 1. What this does for grub2 also applies to when syslinux/extlinux is > the bootloader. There are some situations when it is desireable to have > anaconda do all the configuration it now does but not do the extlinux > --install or install a new MBR or change the active/bootable flag on the > partition. Yeah, whether to look at the behaviour for other bootloaders is an obvious consideration, but BIOS/grub2 is still by far the most important case. > 2. There may be a need for a new kickstart command which specifies a > directory where the /boot files would be installed (kernel, initramfs, > syslinux/extlinux, etc.). In a regular gui install, this directory > could default to using the machine-id with the result that everything > for this install goes into /boot/<machine-id>/ rather than /boot. Yes, > this can be done with a complicated post-install script or after install > process but it would be a lot easier if there were some enabling > capabilities. This isn't something I want to consider as part of the current proposal. I think it would be better considered separately. > 3. There appears to be a lot of effort going into support of UEFI and > currently grub2 is the bootloader because it alone supported EFI. That > is no longer the case since syslinux-6.02 supports the "old" bios as > well as efi64 and efi32. Also off topic from the current proposal, and pjones has said grub2 is used as the UEFI bootloader not because it's the 'only' one - there have always been others, including elilo and gummiboot - but because it's the only one with all the capabilities considered necessary. -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
