Bug 463558
Summary: | [LTC 6.0 FEAT] 201137:Overriding of built-in kernel modules during install | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | IBM Bug Proxy <bugproxy> |
Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 6.0 | CC: | ejratl, notting |
Target Milestone: | alpha | ||
Target Release: | 6.0 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-08-21 20:38:43 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: | |||
Bug Depends On: | |||
Bug Blocks: | 356741 |
Description
IBM Bug Proxy
2008-09-23 21:21:00 UTC
I believe this is more of an anaconda issue. How does the driver update disk not provide this functionality? It seems to me that's exactly what it is designed to do - allow you to use a new kernel driver that includes support for a new piece of hardware that the driver we shipped with did not. What more is required here? ------- Comment From lcm.com 2009-09-16 13:29 EDT------- Evidently, this has already been fixed post RHEL5.2/3. So, as long as that remains true for the RHEL6 installer, then there's nothing to do here and this can be closed. |