systemd: Failed to initialize SELinux context: Permission denied

John.Florian at dart.biz John.Florian at dart.biz
Thu Dec 6 20:39:55 UTC 2012


Bruno Wolff III <bruno at wolff.to> wrote on 12/06/2012 12:10:33:

> On Thu, Dec 06, 2012 at 12:03:20 -0500,
>    John.Florian at dart.biz wrote:
> >
> >I wasn't expecting this behavior -- figured livecd-creator would be as
> >before or better.  I guess for now I need to boot with selinux=0 unless
> >someone has any suggestions for this problem.
> 
> It's normally better to use permissive mode than to disable selinux. You 

> won't be required to relabel to turn selinux on. You will get logs of 
> what accesses are being blocked, so that you can provide a better report 

> on the problem and use a local policy fix if desired to work around 
> the issue.

Yeah, if I was actually worried about security in this case, that would've 
been my usual approach.  I had it turned off to bring greater visibility 
to other errors long before F18 alpha and was waiting for this BZ to move 
along before worrying further about SELinux again.

So do I just need to do a relabel at this point?
--
John Florian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/test/attachments/20121206/f7c88e38/attachment.html>


More information about the test mailing list