SlackwareThis Forum is for the discussion of Slackware Linux.
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.
I seem to run into permissions problems a lot, since I try to do everything from a normal user account. I know that I can modify permissions on devices etc. individually, but I was wondering what others do to overcome things like mplayer not having access to /dev/cdrom, gnome sound device access, mounting network shares, etc... from a normal user account. Some things such as mplayer will not run from an su terminal window. I could just always login as root, but I would rather not, unless i fix X to allow screensavers to run etc...
What does everyone else do about this ? Just add my user account to the root, and adm groups? chown everything that gets in the way ? Is there a correct way to have a "superuser" ?
Listen to Tinkster, his method is "the proper way" (TM). My simple hack was for what's essentially a single-user system I'm the only person using it... it's faster, but not recommended for a multi-user environment.
Originally posted by Tinkster P.S.: Hey Azmeen, thanks for the affero! :}
Just UpGraded to Slack 10.1, VERY nice . . . Thank-You PV!
This time I decided to use a separate account, I'm told it's safer.
But, every time I try to do something as a user I don't have permission.
So, I logout/login as root, make the permission changes, then
logout/login as user and go on to do something else and find that
I don't have premission to do that either, so I do the above allover again.
Then on top of that, some changes I make with Kuser don't stick.
I know the drives I want access to are mounted rw.
As root, I have total power.
How can I allow a user to have access to everything root does
without allowing the user ability to damage the system?
What does everyone else do about this?
Should I stick to being root?
I'm the only one in the house really using Linux.
how did you make the account?
Use useradd instead of adduser.
I did not have many permission problems. I just added my user to some groups, altered fstab a little bit, and changed the permissions in 2-3 device files, and everything worked fine.
Last edited by perfect_circle; 03-11-2005 at 12:41 PM.