On Fri, Apr 1, 2011 at 4:17 PM, cornel panceac <cpanceac@xxxxxxxxx> wrote:
2011/4/1 Scott Robbins <scottro@xxxxxxxxxx>On Fri, Apr 01, 2011 at 11:26:07AM +0200, Joachim Backes wrote:enforcing=0 worked for me.
> >
> >Matej, are you sure, the enforcing=0 works around this? I tried that, and
> >my system still does not boot. Maybe just a bad luck, but selinux=0
> >worked. I'm not sure about the root cause of the problem, but maybe the
> >complete selinux engine needs to be disable to work around it, which is
> >not what enforcing does.
>
> I can confirm this: No booting with enforcing=0, but booting with selinux=0
>
Not sure how things go with people who have selinux turned off. ÂThat
may change matters.
worked for me too. i have selinux enabled in .conf
--
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
enforcing=0 work for me too
yum downgrade systemd\*Â
as root
fixes the issue, until a new systemd + selinux policy hits the repos.
Tim
-- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
