> Hold on... this is not the issue and you're going the Wrong Way(tm).
> When you are root, you can screw the kernel and/or the whole system in
> zillion ways.
Actually, no. Sure, we can't protect from oopses caused by root scribbling
on kernel structures via /dev/kmem.
However! Under _no_ circumstances should the kernel oops trying to unlink
ANY file!! Regardless of if only root can try and unlink it (because he
owns it), and regardless of what file system type.
Hey, only root can use ifconfig, so we'd better ignore any network
configuration related oopses, right?? :)
Cheers
Chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu