Bug 166107
Summary: | Running kudzu after startup produces unexpected results | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Henry Harris <henry.harris> |
Component: | kudzu | Assignee: | Bill Nottingham <notting> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.0 | CC: | kanderso, lhh, rvokal |
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: | 2006-10-17 14:42:58 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
Henry Harris
2005-08-16 23:13:15 UTC
Need more information on what sort of hardware configuration you have on the box. What does /etc/sysconfig/hwconf look like before & after? Note that in the case of adding SCSI *devices*, running kudzu won't actually change any configuration on the system that's used by anything... |