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.
Hello folks, I have recently been tasked to support a couple of linux boxes (RHEL 3) and although I have worked with Linux and Unix before (mostly in a user/operator capacity) I am still mostly a Windows sysadmin.
I have a question regarding the root account. Now I know that you should never run it in a session and to use SU or SUDO for performing administrative tasks, what I wanted to know is what are the ramifications (besides being root equivalent) of creating a "root equivalent" account.
I have created a secondary account using useradd -o (on a test box) in order to force the new acount to use a UID of 0 (root account) and I am able to logon with it fine and provides me with the root prompt.
Since this is now a root equivalent account,
1 - would it be easier to use this account for logons for admin tasks as opposed to having to logon as a user and then run SU
2 - easier to audit an account like this assuming there are going to be multiple admins on this server (don't ask)
The end result I am looking for is to have a few admins who will be on the box and I want to avoid them using the root account itself for daily sysadmin tasks. What would be the best way to accomplish the
Your thoughts on this would be appreciated. Thank you.
What you have done is create an alias for the root account. Whatever apps you run and other things you do on the system will all be done as root because your user has a UID of 0. Where you need multiple admins for a system, create an admin group and then use sudo to give the admin group privileges to run certain commands.