Bug 53923

Summary:	kickstart: lba32 and onprimary option is broken
Product:	[Retired] Red Hat Public Beta	Reporter:	Andreas J. Bathe <ajb>
Component:	anaconda	Assignee:	Jeremy Katz <katzj>
Status:	CLOSED RAWHIDE	QA Contact:	Brock Organ <borgan>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	roswell	CC:	ajb
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2001-09-21 19:24:30 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Andreas J. Bathe 2001-09-21 18:42:59 UTC

Description of Problem:

when kickstarting I realized that the option --lba32 within the bootloader
section wasn't recognized.
when looking up in the source, I saw that there have to be removed the two
dashes, because when using ----lba32 (with 4 dashes) there is no error
message and kickstart process runs through.

also there is some problem with the --onprimary option...

take care
Andreas

Comment 1 Jeremy Katz 2001-09-21 19:36:18 UTC

Boot loader bit fixed... for onprimary, use asprimary instead to force the use
of a primary partition; there is no way to force the allocation of partitions in
a specific order right now, so if you want to have them in a specific order, the
drive needs to be already partitioned (in which case you can use onpart)

Comment 2 Jeremy Katz 2001-11-28 20:58:05 UTC

*** Bug 56784 has been marked as a duplicate of this bug. ***

Comment 3 Jeremy Katz 2002-01-02 22:27:58 UTC

*** Bug 57852 has been marked as a duplicate of this bug. ***

Comment 4 Jeremy Katz 2002-01-16 20:25:06 UTC

*** Bug 56367 has been marked as a duplicate of this bug. ***

Comment 5 Jeremy Katz 2002-03-06 16:04:21 UTC

*** Bug 60762 has been marked as a duplicate of this bug. ***