Bug 431
Summary: | modprobe puts the preferred directory at lowest priority | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | vek |
Component: | modutils | Assignee: | David Lawrence <dkl> |
Status: | CLOSED DUPLICATE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5.2 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 1999-01-07 18:10:27 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
vek
1998-12-15 16:52:50 UTC
The script in /etc/rc.d/rc.sysinit creates a new preferred link everytime the machine boots based on the version of the kernel it detects therefore if you boot a new kernel it should set the preferred link to the directory with the new modules. One thing you should do before doing a modules_install during the kernel compilation is move your old /lib/modules/2.0.x to /lib/modules/2.0.x.old or something like that. That way your old modules do not get overwritten if you want to revert back to an older kernel later. Problem not resolved. See my e-mail messages for further information. |