W dniu 31 marca 2011 17:39 użytkownik Joachim Backes <joachim.backes@xxxxxxxxxxxxxx> napisał: > On 03/31/2011 05:32 PM, Michał Piotrowski wrote: >> >> Hi, >> >> 2011/3/31 Matthias Runge<mrunge@xxxxxxxxxxxxxxxxx>: >>> >>> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA1 >>> >>> Hello, >>> >>> the subject says all: >>> Since systemd(?) update an hour ago, my test system does not boot any >>> more. removing "rhgb quiet" from kernel command line shows >>> Failed to load SELINUX policy >>> Failed to set security context... for /run: invalid argument >>> Failed to set ... for /sys: Invalid argument >>> Failed to set ... for /sys: Invalid argument >>> Failed to mount /sys/fs/cgroup/systemd: No sich file or directory >>> >>> Did someone else see this? How to repair such a broken system? >> >> Problem of the same category here >> https://bugzilla.redhat.com/show_bug.cgi?id=692573 >> >> I need to find out how to boot into emergency... solution should be >> simple - systemd downgrade > > Or boot with "selinux=0" I have not tried this, because I don't have SELinux installed - I disabled it after installation and later I removed selinux-policy package. It appears however that SELinux works without selinux-policy package and /etc/sysconfig/selinux file disappeared... wtf? Thanks for the hint. You've saved me several hours searching to solve this problem. I never imagined that something that is not installed can be the source of the problem :) > > -- > Joachim Backes <joachim.backes@xxxxxxxxxxxxxx> > > http://www.rhrk.uni-kl.de/~backes > > -- Best regards, Michal http://eventhorizon.pl/ -- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test