Re: Does "--asprimary" make any sense when doing GPT partitioning?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Nov 12, 2014 at 03:53:00PM -0600, Spike White wrote:
> All,
> 
> In a ks.cfg when doing MBR partition, I realize the value of --asprimary.
> Here's an example:
> 
>    part /boot --fstype ext3 --size=300 --asprimary
>    part pv.2 --size=38000 --grow --asprimary
>    volgroup osvg pv.2
>    logvol / --fstype ext4 --name=root.fs --vgname=osvg --size=4000
>    ....
> 
> But when doing GPT partitioning (i.e.,  inst.gpt in your grub.conf kernel
> line), does --asprimary even make sense?
> ksvalidator didn't flag it as an error, so syntactically it's legal.
> 
> Is it just ignored by the part command if doing GPT partitioning?

Correct, on gpt it doesn't have any effect, it is only used for msdos.

-- 
Brian C. Lane | Anaconda Team | IRC: bcl #anaconda | Port Orchard, WA (PST8PDT)

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list




[Index of Archives]     [Kickstart]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]
  Powered by Linux