Bug 53923 - kickstart: lba32 and onprimary option is broken
Summary: kickstart: lba32 and onprimary option is broken
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: anaconda
Version: roswell
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Brock Organ
URL:
Whiteboard:
Keywords:
: 56367 56784 57852 60762 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-09-21 18:42 UTC by Andreas J. Bathe
Modified: 2007-04-18 16:37 UTC (History)
1 user (show)

(edit)
Clone Of:
(edit)
Last Closed: 2001-09-21 19:24:30 UTC


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2002:016 normal SHIPPED_LIVE Various anaconda installer fixes 2002-01-17 05:00:00 UTC

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. ***


Note You need to log in before you can comment on or make changes to this bug.