On Wed, 2012-08-15 at 18:29 -0700, Steve Rikli wrote: > On Tue, Aug 14, 2012 at 09:08:10AM +0200, Richard Neuboeck wrote: > > I've got an answer from David Lehman how the decision process for the > > usage of biosboot works in anaconda: > > > > Here is the entire decision tree: > > > > - did the system boot in EFI mode or BIOS mode? > > - EFI > > - use gpt and never make biosboot > > - BIOS > > - is the disk larger than the max for msdos (2TB)? > > - yes > > - use gpt and ensure there's a biosboot partition > > - no > > - use msdos > > Either I'm not following that logic or I think something isn't behaving > as advertised. Here's my situation .... > > I have a bog standard Dell PowerEdge 1850 -- same test machine I used in > the initial Fedora 16 work that prompted me to start this thread -- which > has no EFI, and boots from an old & small (20GB) SCSI disk. > > If I read the above correctly, I should _not_ need a biosboot partition, > yet a Fedora 16 Kickstart install fails with the known partitioning error > mentioned in bugzillas et al, unless I create one. > > What am I missing? I believe this logic applies only to Fedora 17. In Fedora 16, there was an attempt to have all systems using GPT (and thus some of them biosboot partition), unless you used 'nogpt' command line option. However it appeared that some systems have problems with such setups and thus aforementioned logic was introduced in Fedora 17. -- Vratislav Podzimek Anaconda Rider | Red Hat, Inc. | Brno - Czech Republic _______________________________________________ Kickstart-list mailing list Kickstart-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/kickstart-list
