Username or EmailPassword
I fully agree with ponds; a good administrator should be able to secure a system perfectly by himself. If you don't, buy some good (O'Reilly) books about security. Learn how to secure a system (instead of relying on "secure" packages, or automatically applied kernel patches), and apply patches like grsecurity *when* you need them in a situation. Things like SELinux and grsecurity are perfectly documented...
Tell me, who do you secure a system against buffer overflows, stack overflow, stack smashing, ipc compromises, memory corruptions, root exploits, race conditions, to mention a few?
Since I really don't know how, you might as well begin to school me of how to secure a system "(instead of realying on "secure" packages, or automatically applied kernel patches)."
If somebody is not able to secure a system by himself, he/she is not a good system administrator and should think twice about administrating cruscial production machines.
Yeap, real admins don't need docs, right?