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

For bugs related to Red Hat Enterprise Linux 5 product line. The current stable release is 5.10. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 464669

Summary:	documentation: add info about how to load modules before others
Product:	Red Hat Enterprise Linux 5	Reporter:	Jeff Bastian <jbastian>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED WONTFIX	QA Contact:	Release Test Team <release-test-team-automation>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5.2	CC:	emcnabb, tao
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-09-30 14:29: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 Jeff Bastian 2008-09-29 20:49:06 UTC

+++ This bug was initially created as a clone of Bug #151778 +++

Anaconda has had an undocumented command line option 'driverload=____' for some years now.  Occasionally this comes in handy when working with fussy hardware.  Can it be added to command-line.txt?

This request was rejected 3 years ago because it's not a guaranteed interface.  But it's still in anaconda today, so it would be nice to have it documented, even if it comes with a warning that it may go away in favor of a better solution someday.


--- Additional comment from katzj on 2005-03-22 10:27:03 EDT ---

The driverload paramter is not documented because it's not a guaranteed
interface.  It was added to address a specific problem for one release and we
reserve the right to pull it in future releases for a more complete solution to
the problem.

Comment 1 Chris Lumens 2008-09-30 14:29:30 UTC

The problem is that once we document it (even if we do say it's liable to go away), people are going to start relying on it and then we'll never be able to get rid of it if we need to.