i ve just installed fc 6 and get this err.

boot with the enforcing=0 option in the grub string and you should be fine. Then update the policies with yum and if it still fails to boot I would suggest

whilst disabled, then re-enabling afterwards. Let us know how you get on.

Regards
Chris

OK Chris you are my hero... I posted in another thread about FC6 not booting on my laptop. I tried your suggestion here not expecting anything... well darn if it didn't boot. I got some things to work out on the setup but it worked.

Now what do I have to do? IT boots, but what is problem? and why does this keep it from segfaulting out during the bootup?

I guess go google enforcing=0

edit:
OK I got it. Seems that disables selinux (something new to me) and because my /home directory from a previous distro was a reiserfs partition selinux did not like it and it wacked the system up, for lack of technical terms.

Hey JollyRogers,

Great to hear it helped you out! The problem is pretty much what it says - it cant locate the appropriate SELinux policy (i.e. enforcing) and so cannot apply the necessary security controls, hence the kernel panic. Although I haven't looked at this too much myself, I would be inclined to switch the selinux policy to permissive and see if you have the same problem. You could also install setroubleshoot, which does what it says.

Cheers
Chris

Chris,
Apparently SELinux does not play well with reiserfs. I ended up backing up my /home which was sitting on a reiserfs partition, after getting it to boot with enforcing=0 and formating the partition w/ ext3 and mounting it as my /home. It all works great (cept trying to get the nvidia drivers going...but that is an easy fix).

This was a test on my laptop to demonstrate fedora to some IT people at work. I was even considering putting it on my home tower... it has slack 9 or 10 on it now , but I just looked at my fstab and I used resierfs on my box, and have a lot of stuff on those partitions. So I guess I will use fedora on the laptop and stick to slackware on my home box and just do an upgrade w/ slack11.

Thanks again for your suggestion! Even though it was not directed at me it fixed my problem.