Bug 179092
Summary: | unbootable becasue selinux denies access to ld.so.cache and libuuid.so.1.2 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Andy Burns <fedora> |
Component: | selinux-policy | Assignee: | Daniel Walsh <dwalsh> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-01-28 21:55:57 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
Andy Burns
2006-01-27 12:29:37 UTC
You need to relabel your system. touch /.autorelabel reboot You might have to boot in permissive mode. Any time you run with selinux=0 files will get mislabeled. You are always better to boot with enforcing=0 so that file contexts are maintained. the relabel fixed it, is the mere presence of the .autorelabel the trigger, or it's timestamp relative to something else? Thanks for the enforcing=0 tip too, I still have quite a blindspot about selinux, so it seems that jumping to selinx=0 can be a short term cure, but longer term headache, though many people on the devel and test lists recommend selinux=0 at the first hint of an selinux issue :-( That is unfortunate. Next time you see it maybe you can make this comment. |