Bug 385
Summary: | Can't mount write-protected ext2 floppies | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | hargrove |
Component: | autofs | Assignee: | Cristian Gafton <gafton> |
Status: | CLOSED WORKSFORME | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 5.2 | ||
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: | 1999-03-19 18:50:46 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
hargrove
1998-12-11 09:00:13 UTC
Yes indeed, when a write-protected disk is attempted to be mounted with autofs, one gets the error that the mount point does not exist. Confirmed in test lab. This bug has been assigned to a developer. The two most recent comments (by jturner and dkl on 12/11/1998) describe the bug as "VERIFIED" and then as "ASSIGNED". And yet bugzilla shows a status of "RESOLVED". Why? I've just verified that this bug is still present in RHL 6.0 (autofs-3.1.3-2 and e2fsprogs-1.14-4) so I'd not call that resolved. Commit pushed to master at https://github.com/openshift/openshift-docs https://github.com/openshift/openshift-docs/commit/0aee001f803e1565c37adc66a7acb61f81086c64 Merge pull request #1068 from bfallonf/issue_385 GH issue #385: added para on logoutURL |