On Thu, Mar 31, 2011 at 05:39:41PM +0200, Joachim Backes wrote:
On 03/31/2011 05:32 PM, MichaĆ Piotrowski wrote:
>Hi,
>
>>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 thought that enforcing=0 was considered a better option, no, as it
avoided relabling. (I would be grateful if someone can either confirm
or correct that statement.)
Yet another reason setting grub's timeout to 0 was a very bad idea,
especially in VMs.
--
Scott Robbins
PGP keyID EB3467D6
( 1B48 077D 66F6 9DB0 FDC2 A409 FA54 EB34 67D6 )
gpg --keyserver
pgp.mit.edu --recv-keys EB3467D6
Xander: Okay, this is starting to grate my cheese. These
woods aren't that big. Now, I know we've beein going straight because
I've been following the North Star.
Willow: Xander, that's not the North Star. It's an airplane.
Xander: No, that's not an airplane. That's definitely...a blimp. But I
can see how one would make that airplane mistake.