Hi Jeff - On Thu, 2001-11-01 at 18:32, Jeff Lane wrote: > --onprimary AFAICT IS in Anaconda, and apparently works fine IF you do a > manual install, and specify that a certain partition, i.e. /boot, be > forced to be a primary, in disk druid. However, the problem arrises when > specifying --onprimary in a kickstart script. Right, anaconda lets you specify primary partitions manually, but not in kickstart: [root@stout anaconda-7.2]# grep -r onprimary * [root@stout anaconda-7.2]# > My personal belief is that this is something that was left out of the > kickstart portion of anaconda, (maybe something called by kickstart.py) > but not in the manual portion. msw said yesterday that --onprimary no longer works with parted, or something along those lines... also that --asprimary will allow you to specify that it should go on _a_ primary partition, but --onprimary (specifying a _particular_ partition) doesn't work anymore. Perhaps just dropping it from ksconfig and the docs is the solution. -Eric -- Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs sandeen@xxxxxxx SGI, Inc.
