From: "Chmouel Boudjnah" <[EMAIL PROTECTED]> | "Thomas Backlund" <[EMAIL PROTECTED]> writes: | | > Ouch... | > I forgot to tell you that it's the secured kernel 2.4.21preX-1mdksecure | > that I'm running on this box..., sorry... | > I just installed the "normal" 2.4.21pre4-1mdk kernel, | > and it works as it should... | > So... What next... | | that help a lot :-(. Can you test with the 2.4.21-0.pre3.2mdk i wonder | if i didn't screwd up things with xfs.... |
Huh... if the standard pre4 mdk works the xfs didn't break the system... BTW where can I get pre3.2 since it's not on my mirror anymore... but... to repeat myself... here is the kernel that I have tried: kernel-2.4.21.pre2.1mdk-1-1mdk WORKS kernel-2.4.21.0.pre4.1mdk-1-1mdk WORKS kernel-secure-2.4.21.pre2.1mdk-1-1mdk WORKS kernel-secure-2.4.21.0.pre3.1mdk-1-1mdk FAILS kernel-secure-2.4.21.0.pre3.2mdk-1-1mdk FAILS kernel-secure-2.4.21.0.pre4.1mdk-1-1mdk FAILS since the problem seems to be "security" related... since it only shows up in the secured kernel, i noticed this line in the pre3.1 changelog * grsecurity 1.9.8. correct me if I'm wrong, but haven't there been problems before with the grsecurity patches / code... Maybe I should rebuild the 'mdksecure' kernel with those grsecurity options according to the standard 'mdk' kernel, and se if it helps... Any thoughts... Thomas
