Bug 41570
Summary: | How does kudzu work ? | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Derrien <derrien> |
Component: | kudzu | Assignee: | Bill Nottingham <notting> |
Status: | CLOSED NOTABUG | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.1 | CC: | bertola, rvokal |
Target Milestone: | --- | Keywords: | FutureFeature |
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2001-05-21 18:14:44 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
Derrien
2001-05-21 13:01:17 UTC
It's done by the updfstab program; it's run by the kudzu init script, but it's *also* run on PCMCIA storage insertions, for instance. How to prevent the creation of the new entry in fstab anyway? (the new entry in fstab cannot be unmounted by non root users, it is extremely annoying Moreover it changes the symlinks /dev/cdrom and /dev/cdrom1 and keeps adding directories to /mnt/ Also very annoying.... Thanks |