Bug 112857
Summary: | mkinitrd doesn't support upcoming libata module | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Peter Bieringer <pb> |
Component: | mkinitrd | Assignee: | Jeremy Katz <katzj> |
Status: | CLOSED NOTABUG | QA Contact: | David Lawrence <dkl> |
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-01-04 18:34:12 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
Peter Bieringer
2004-01-04 10:07:39 UTC
mkinitrd shouldn't need any special code here... Does the sata_promise module not have a module dependency on libata? Perhaps, but does module dependency help on using "insmod" like the boot loader does? Why was "scsi_mod" hardwired added by "mkinitrd" if not because of similar reason? Yes, mkinitrd parses the modules.dep file and makes sure that all of the dependent modules are there. sd_mod is "special" because while there really isn't a dependency of the host adapter module on sd_mod (you could just have a cdrom attached for example), to be useful for the initrd case, you need to have sd_mod. Looking at the modules.dep for the 2.6 kernel I'm currently running, it looks like the module dependency is there, so everything will work fine assuming depmod -a is properly run after the modules are installed. Ok, you're right about the use of modules.dep, but this is only implemented in the FC1 release. At least RHL 9.0 do not show any modules.dep support. |