<tt><font size=2>Bruno Wolff III <bruno@wolff.to> wrote on 12/06/2012
23:48:07:<br>
> On Thu, Dec 06, 2012 at 15:39:55 -0500,<br>
> John.Florian@dart.biz wrote:<br>
> ><br>
> >Yeah, if I was actually worried about security in this case, that
would've<br>
> >been my usual approach. I had it turned off to bring greater
visibility<br>
> >to other errors long before F18 alpha and was waiting for this
BZ to move<br>
> >along before worrying further about SELinux again.<br>
> ><br>
> >So do I just need to do a relabel at this point?<br>
> <br>
> Once you boot with selinux enabled, a relabel should happen automatically.<br>
</font></tt>
<br>
<br><font size=2 face="sans-serif">That didn't seem to work; I got the
same lockup with the permission denied message. I even had touched
/.autorelabel (not realizing the relabel should happen automatically).</font>
<br>
<br><font size=2 face="sans-serif">Thinking selinux might be preventing
the relabel from happening (?!?) I rebooted with selinux=0 so that I could
reconfig /etc/sysconfig/selinux having SELINUX=permissive, touched /.autorelabel
and rebooted again. This time I saw the relabel process do its thing
and trigger a reboot. I then went back to reconfig /etc/sysconfig/selinux
having SELINUX=enforcing, rebooted and all seemed well, finally.</font>
<br>
<br><font size=2 face="sans-serif">So, I'm all good now, but there may
be some bugs in that "</font><tt><font size=2>relabel should happen
automatically</font></tt><font size=2 face="sans-serif">" bit.<br>
--<br>
John Florian</font>
<br>