Christian Weisgerber wrote:
Stijn <[EMAIL PROTECTED]> wrote:
1. don't log in remotely as root.
There is no good reason not to. In fact, if you don't work on a
machine and just have it sitting in a corner moving packets, there
is no point in even creating a user account.
2. don't use bash as shell for root.
Or at least understand what you are doing.
3. and if you really want to ignore good advice 1 & 2, adapt your PATH
variable to include /usr/local/lib/.
That is complete nonsense.
Well I'm not going to argue about the benefits of whether or not logging
in as root, that depends on numerous reasons. There are enough threads
about that in the archives. The point is, this guy shot his foot off
when changing his root shell (which is probably dynamically linked) and
locked himself out. Now, he has at least one solution to avoid that in
the future.
Like you said so well, "at least understand what you are doing".
All the best,
Stijn
