Bug 85985 - kickstart device command not working.
kickstart device command not working.
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
9
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
Mike McLean
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-03-11 16:46 EST by Mike McLean
Modified: 2007-04-18 12:51 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-10-04 23:07:33 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Mike McLean 2003-03-11 16:46:11 EST
Tried something like 

device scsi aic7xxx --opts=verbose

in ks.cfg, but this option did not make it into modules.conf (neither anaconda's
or the one in sysimage).
Comment 2 Jeremy Katz 2003-04-02 00:09:21 EST
We read the kickstart config after the module is loaded so there's not a lot we
can do.  Have some ideas on how to move things around written on a sheet of
paper beside my desk that I should dump here instead :)
Comment 3 Jeremy Katz 2004-10-04 23:07:33 EDT
Added a nonet and nostorage option so that you can load needed devices
with options via your ks.cfg.  

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