Selinux so badly corrupted machine can't start [Solved]
Claude Jones
claude_jones at levitjames.com
Tue Jun 19 02:27:59 UTC 2007
On Monday June 18 2007 8:19:43 pm Claude Jones wrote:
> I'm going to boot in
> permissive mode and establish the labeling as just Dan Walsh
> suggested - I shall report back results
OK - I run KDE; while booted up with selinux=0 as a kernel parameter, I went
into the Administration/Firewall and SELinux GUI and set selinux to
permissive; then I ran as root from a terminal "touch ./autorelabel"; the I
rebooted and didn't append anything in grub to the kernel line; the machine
went through a pretty standard boot and right after starting udev, it went
into its relabeling routine. Several minutes later, it continued to boot
normally and came up - I logged in, went to KMenu/Administration/Firewall and
SELinux GUI and set selinux to enforcing - I rebooted.
Now, it booted it up fine
Thank you Daniel
I'll have to see how packagement goes over the next few days, but it seems
the near-perfect storm has abated
--
Claude Jones
Brunswick, MD
More information about the fedora-list
mailing list