Bug 1044541
Summary: | Consider making SELinux a REQUIREMENT, not recommendation. | ||
---|---|---|---|
Product: | [Retired] Fedora Documentation | Reporter: | Mike Lieman <mikelieman> |
Component: | install-guide | Assignee: | Pete Travis <me> |
Status: | CLOSED EOL | QA Contact: | Fedora Docs QA <docs-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | devel | CC: | botsch, chupaka, jnicol, juhani.jaakola, me, pbokoc, relnotes, wb8rcr, zach |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2024-05-21 09:21:52 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1136030 |
Description
Mike Lieman
2013-12-18 14:14:14 UTC
We will track the associated bug and take this into consideration when updating fedup documentation, thanks for the report. Upgrade documentation has the greatest presence in the Installation Guide, so I'm reassigning your bug to it and will do the work there. Feedback on IRC support volunteers should be directed to https://fedorahosted.org/irc-support-sig/ ; updated documentation can't fix anyone's behavior or increase their willingness to support use cases they don't endorse. If SELinux is required, I will be finding a different distro. *** Bug 1008742 has been marked as a duplicate of this bug. *** SELinux has caused me a lot of problems in the past, so I have always disabled it. If SELinux is required in Fedora, I'll switch to a different distribution. The install guide has been retired, therefore I'm closing this bug. If you would like to report Fedora docs bugs in the future, please use the "bug" icon on the top right of the affected page, it will take you directly to the appropriate issue tracker. |