Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
If you do it despite the advice then you just create a user with UID 0 like root. Users are really known by their UID number rather than their name. Anyone with UID 0 has root authority even if you give it a user name like billybob. Make sure the user appears AFTER the real root user in /etc/passwd.
If you're giving someone wide open access you might as well give them the root password itself as there will be no difference in their level of authority. Why waste time with an unnecessary account?
A BETTER IDEA:
Rather than doing the above however it is much better to install and use sudo if you need to give root level access to another user. With sudo the user must login as themselves then must run the sudo command to execute whatever task you've allowed them to do as root. The benefits to using sudo:
1) You restrict users to ONLY those commands they need root access for instead of givng them wide open access.
2) It logs every time the user uses sudo so you'll know when billbob has blown you out of the water.
3) You can even use sudo to give users access to other global accounts (like Oracle) so that you can tell what individuals have done with that global account instead of guessing which one of the DBAs did a cat /dev/null >production.dbf.
jlightner is 100% correct. There should only be one root account, and operating with root privs should only be done in specific, limited situations (such as installing new packages, recompiling the kernel, etc)