Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then 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.
nah, my way is nicer. and it makes more sense to add the user to root as an additional group, rather that just using root as the main group. you should be able to create a normal user gid > 500 as a memerb of the root group, you'll get less error warnings and such lik as well i presume. not actually BEING root there might be a few things they couldn't do, if the group mask is not set on certain files. your way simply renames root to someone else, which i would guess could very easily screw a system over.
Yeah, I know, thus the warning in my message. Actually I've tried it on other systems and it doesn't screw things up... all it does is allow you to have another name/password to become root, because once you login, the system still equates you to uid 0 and you just look like root. You don't even have the new username.
Just putting a user in the root group doesn't give him "all the rights of a super user(root)" as the poster requested. At most it gives permissions to some of roots files.
I have a hunch that sudo will accomplish what he's wanting, but until we know exactly what that is, there's no way to tell... maybe he wants to rlogin from another system as a regular user and become root on the Linux machine /shrug.
If he's wanting all of root's rights, why doesn't he just use root's account?