<div dir="ltr"><div>Hi,</div><div><br></div>One of the reasons I'm using Fedora is because the exceptional support for SELinux and auditd that so far - despite a known incompatibility with Docker + Btrfs - is working great.<div><br><div>Said that, kudos to everyone who makes SELinux integration such smooth.<div><br><div class="gmail_quote"><div dir="ltr">On Tue, Jun 23, 2015 at 1:36 AM Kevin Wilson <<a href="mailto:wkevils@gmail.com">wkevils@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Dan,<br>
Thanks a lot for your reply.<br>
In fact, I ran<br>
pm -e selinux-policy-targeted<br>
rpm -e selinux-policy<br>
And after reboot I got some message about freeze from systemd, I could<br>
not login (tried twice), so I reinstalled Linux on this machine.<br>
The question is: what do you mean by "If you disable SELinux".<br>
<br>
Does that mean adding "selinux=0" on command line?<br>
Or is it enough to set, in /etc/selinux/config<br>
<br>
SELINUX=disabled<br>
<br>
(or maybe better is SELINUX=permissive, as Ali suggested ).<br>
Regards,<br>
Kevin<br></blockquote><div><br></div><div>Yes, as Ali suggested in this particular use case the best approach would be to set SELINUX=permissive and reboot.</div><div><br></div><div>Regards,</div><div>-Martín</div></div></div></div></div></div>