Howdy,
There is a bit if incorrect information in this thread that should be corrected...
First off if you have not "activated" the root account it does not have a password. This is a good thing with no password it cannot be cracked
So how does the admin do root things? Via the sudo command which is set uid root. Huh? what does that mean? It means that when the program is run it runs as the owner of the file and not the user that started it. You can see this from the s in the permissions on sudo below.
eric% ls -l /usr/bin/sudo
---s--x--x 1 root wheel 96384 Sep 14 19:16 /usr/bin/sudo
When you run sudo it has its own set of checks it runs, one thing it does it verify that you are who you should be. That is when it asks for a password but that is
the user's password not root's (who doesn't have one remember.)
A cool feature of sudo is that it is possible to specify specifically what commands a given user can use via sudo. At my old university they used sudo to give all the grad students
the ability to arbitrairly kill print jobs, even those which were not their own.
This was a great solution if someone printed a malformed postscript document (resulting is 300 pages of raw postscript garbage) anyone who noticed it could kill the job. Oh yeah, also sudo actions are logged so you could not abuse this power to shortern the print queue without leaving a paper trail.
Finally, someone mentioned you needed to log on as root to have a root shell. Not so, just use sudo to start a shell using
sudo tcsh
Have fun,
-Eric