Bug 140981
Summary: | /selinux is not allowed by the Filesystem Hierarchy Standard | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | taj <taj> |
Component: | libselinux | Assignee: | Daniel Walsh <dwalsh> |
Status: | CLOSED NOTABUG | QA Contact: | Mike McLean <mikem> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | taj |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://www.pathname.com/fhs/pub/fhs-2.3.html#THEROOTFILESYSTEM | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2004-11-29 01:21:47 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
taj
2004-11-27 11:36:02 UTC
Fixing this involves convincing the upstream SELinux maintainers otherwise. SELinux isn't an "application"; it's part of the OS, and the OS can create any paths it wants to: "Distributions should not create new directories in the root hierarchy without extremely careful consideration of the consequences including for application portability." There's no application portability concerns, thus no issue. But it would be useful to standardize /selinux in the upstream FHS. |