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!
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I understand the fundamentals of a multiuser OS, with permissions and access rights and so forth to certain files, as I have been a user on large UNIX servers.
Now, however, I run my own Linux server and basically act as administrator to my personal machine.
When I installed Linux on the machine I was told to create a user account for myself, however, when I go into Linux to do my daily functions, I find that I have to su to root to accomplish many tasks.
For a one user scenario, what are the advantages/uses of a multiuser environment? Should I be granting my personal account more priveleges and doing more work from that account?
Lets just say that as user you're less likely
to be the victim of an exploit than when you
are a "normal" user ... and the extra effort
of "having to su to do things" should become
less over time, or you haven't set your things
up properly ;)
Also the accidental damage that you can
cause is less as a normal user :}
Distribution: Slack Puppy Debian DSL--at the moment.
Posts: 341
Rep:
When I am root, one moment of inattention results in a restoration from backup.
When I am "user", I have to go through the process of becoming su to hose everything up.
I honestly didn't know it made it easier for a loser to use a "root-kit" when I'm running as root. Say it isn't so. Really?
If security is busted on an application exposed to the internet, aren't I pretty much hosed whether I surfed as root or not? I noticed that the way that many applications install has changed pretty dramatically in the last year or so, I don't have to make many changes from the defaults any more. But I have to admit, I've been lazy and surfed as root--well, if tech sites count as surfing. (I been told that as root, any application I use is possibly going to have root privileges because user privileges can be inherited. It is something I've taken as true, but don't understand.)
Should I be granting my personal account more priveleges and doing more work from that account?
The beauty of it is that you may do as you wish.
If you are wise it is a mix of what you feel is necessary and useful. If you are a little silly is is based on what you find to much bother.
Personally I find that using "su" is no trouble.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.