Bug 193456
Summary: | modprobe cannot remove modules that have been renamed | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Brian Carp <admin> |
Component: | module-init-tools | Assignee: | Jon Masters <jcm> |
Status: | CLOSED NOTABUG | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.0 | CC: | jbaron |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-03-22 16:12:45 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
Brian Carp
2006-05-29 05:30:31 UTC
I will add this to the TODO for upstream. Actually, now I'm inclined to say this is *not* a bug. modprobe -o is intended for module testing, temporarily renaming a module. modprobe uses the modules.dep file for name tracking, so you end up having to use rmmod directly if you rename the modules in this way - which actually will fail in future since the key signature check will balk on the rename too. Can you give me an example of a situation where this is causing a problem? other than renaming on the command line? Jon. |