FC4 is fucked

[H_TeXMeX_H]

FC4 refuses to boot properly ... I'm getting lots of permission denied errors for rather important files. So I'm stuck using command line and lynx (many thanks to the makers of this awesome browser) ... anyway looks like I gotta install FC5, but I still want to know what the fuck happened, so here is the demsg

I hope it the attachment works ... I'm using lynx after all ... it's different.

[verwijderd door de beheerder]

[KernelPanic]

It sounds like SELinux is tripping you up. Try adding selinux=0 boot parameter. (Press 'a' at the grub menu to append the option)

Assuming this works you would then be advised to:
A) reinstall the selinux-policy RPM
-or-
B) Disable the bag of **** completely.

[mobrien_12]

ACtually, I'm suprised networking is functional.  The messages seem to indicate that SELinux is having problems with ifconfig ...which controls your network device setup.

[H_TeXMeX_H]

I fucking hate SELinux ... it causes so many fucking problems !!! There are tons of problems on FC5 caused by it ... and FC4 too. Looks like SELinux was the cause.

What I want to know is what happened between last night and this morning that caused SELinux to fuck up. It was working fine last night, and then in the morning ... it won't boot properly ... what the fuck happened in-between ? We may never know.

Thanks for the responses ... I still switched to FC5, maybe it won't fuck up. Do all distros come with SELinux ? Is it useful at all ?

[piratePenguin]

I just heard about AppArmor today, which looks like a better SELinux-like thing for newbie distros.

Maybe you were cracked...? Modifying SELinux policies would probably be the dream of any (stupid) cracker... But then, it would depend on what services you have open to the internet, and their versions.

[mobrien_12]

I'm not an SELinux expert, but it's pretty cool from what I've read about it.  You know how basically with *nix systems if root gets compromised you are totally hosed?  Well SELinux puts controls on root so cracking root means the entire system isn't compromised.  It's a whole new quantum level of security, but because it puts limits on root, it can cause problems when misconfigured.

Did you do ANYTHING to the box?  Update RPMS?  install something?  What do your system logs say?

Does tripwire say anything has changed?

[H_TeXMeX_H]

Only way my system may have been compromised was through sendmail ... which I have chosen not to install on FC5, but was there on FC4.

Prior to this crash I updated the system as usual ... yum update --exclude=kernel (I was running an older kernel to stay away from the ambiguous "..MP-BIOS bug: 8254 timer not connected to IO-APIC" error). I also messed around a bit with the grub.config adding the noapic flag to the newer, buggy kernel ... I think this may have a lot to do with it. It booted fine with noapic the first time ... the night before it screwed up, then I removed the noapic, and it also booted fine, and then it didn't boot fine in the morning.

[cymon]

Mabye FC is the problem, not SELinux.

[H_TeXMeX_H]

Possible ... I now keep some live CDs around just in case it happens again. I used to have Knoppix and DSL around, but I loaned them to a friend to try em out ... hey I wasn't using them too much. But I just burned another copy of DSL. DSL is the best damn live CD ever ... it's so damn fast (especially if you write it to ram) :thumbup: ... now if only I could run OpenOffice 2.0 on it ... I'll figure something out.

[mobrien_12]

I have never seen this with FC4.