On Fri, 2012-07-13 at 10:18 -0500, David Lehman wrote: > > On Thu, 2012-07-12 at 18:33 -0400, Máirín Duffy wrote: > doesn't mean we wipe that single disk. Instead, we autopart any > > > pre-existing free space on the disk. If that isn't enough space, we > > > automatically shrinkany filesystems as needed. > > And how will we configure the bootloader in this case? If we don't feel > comfortable removing existing partitions from disk, do we feel > comfortable removing their existing bootloader without asking? Hm, let's walk through the bootloaders involved maybe? Pre-existing Fedora / Red Hat / CentOS / etc install - Can we add an entry to the existing one? Pre-existing Linux install - likely to be grub. Do we have to remove it or can we add an entry to the existing one? Pre-existing OS X install - Will Woods had an idea for detecting OS X machines. So we could maybe give any pre-existing OS X users some kind of special message, like, 'go to bootcamp' or whatnot. We better not blow away their OS X bootloader unless they just want to wipe it all (+1 to those folks.) What kind of config is needed to chainload the linux install for Macs? If it requires manual config, is there any way to have some kind of walkthrough for doing that manual config available and referenced both in the installer and elsewhere? Is that manual config hard? Pre-existing Windows XP and up install - Same thing here, better to not blow away and chain load? What manual config is involved here? Also, is there ever a case where it's possible to blow away the pre-existing OS X or Windows bootloader and configure grub to point to the boot sector instead? ~m _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
