Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 85985

Summary:	kickstart device command not working.
Product:	[Retired] Red Hat Linux	Reporter:	Mike McLean <mikem>
Component:	anaconda	Assignee:	Jeremy Katz <katzj>
Status:	CLOSED RAWHIDE	QA Contact:	Mike McLean <mikem>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	9
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2004-10-05 03:07:33 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 Mike McLean 2003-03-11 21:46:11 UTC

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 05:09:21 UTC

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-05 03:07:33 UTC

Added a nonet and nostorage option so that you can load needed devices
with options via your ks.cfg.