Email address obfuscation in effect -- please
click here to turn it off.
[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
"sudo" allows one to execute programs in either a user's $PATH by name
or any program if full path is given with root-level permissions. "su"
changes your identity to root and thus changes the path to /usr/sbin,
etc. "sudo" must be given for each command but "su" needs only to be
called once in the shell session. "sudo" is safer because you have to
intentionally call it for each command. Does this help?
Phillip
Mike Miller wrote:
On Wed, 6 Jul 2005, Phillip Kelchen wrote:
P.S. I just remembered that KDE 3.4 won't even let you log in as root
unless you change the line that says "Allow root login" to "true" in
the config file. It will by default pop up an error message that says
that root login is not allowed.
I don't know why anyone should ever log into KDE as root. It is best
to log in as a user, then use "su" in a terminal window to become root
when needed. Apparently, "sudo" is an even better option than "su"
but I haven't used it much yet. (I'm used to "su" because it has been
around longer.)
Mike
_______________________________________________
members mailing list
EMAIL:PROTECTED
http://mlug.missouri.edu/mailman/listinfo/members
_______________________________________________
members mailing list
EMAIL:PROTECTED
http://mlug.missouri.edu/mailman/listinfo/members