On Oct 27, 2013, at 7:06 AM, Gene Czarcinski <gene@xxxxxxxxx> wrote: > OK, now I wanted to look at anaconda-ks.cfg to see want anaconda used to specify this special partition ... nothing! > > OK, do I write this up as a bug or an RFE. Bug against Fedora 20. But aren't the GUI options effectively translated into kickstart commands behind the scenes? I think there must be a way to do this in kickstart, it's just not obvious. I'd say tomorrow you go to IRC on freenode, and ask what flag to use for GPT biosboot on #anaconda. Anaconda is a Monday to Friday thing. > Yes, I know that I can go in and preallocate the partition manually but the whole idea of kickstart is to do all of this stuff automagically. Well you'd need to look at the code to see what the effect of the 'gpt' line is, there may be some automagic stuff like it causing parted to create gpt instead of msdos disklabels. But there's also code to identify if the platform is UEFI or BIOS, and if the disk is bigger than 2TB, either of which will also trigger the use of gpt instead of msdos disklabels - presumably without having to inform the installer via kickstart. > I assume we will be needing this stuff for UEFI and we will be doing UEFI under KVM as well. Yes, via OVMF. http://www.linux-kvm.org/page/OVMF But there's supposedly a FAT license issue that prevents that project from being included with Fedora. For the purposes of implementing UEFI, it's a free license, so I don't understand what the problem is. https://fedoraproject.org/wiki/Testing_secureboot_with_KVM#EDK2_Licensing_Issues Chris Murphy _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
