Visit Jeremy's Blog.
Go Back > Forums > Linux Forums > Linux - Newbie
User Name
Linux - Newbie This 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!


  Search this Thread
Old 01-08-2006, 02:48 AM   #16
Senior Member
Registered: Dec 2005
Location: Brisbane, Australia
Distribution: Slackware64 14.0
Posts: 4,138

Rep: Reputation: 166Reputation: 166

It sounds like it was done automatically when Linux was installed and yes it's because the drive was previously used with Windows. The fastest way to give your normal user account write access to that file system is to edit /etc/group and add your username to the users line:


Since the file system is read/write for users in that group, it should fix the problem. I'm hoping this works as you need it to, re-formatting or re-installing should always be a last resort
Old 01-08-2006, 02:59 AM   #17
Registered: Oct 2004
Location: Belgium
Distribution: Slackware 13.37
Posts: 512

Rep: Reputation: 31
Originally Posted by prabuayyappan
set the uid in
/etc/passwd as 0

for example
pp:x:508:508::/home/pp:/bin/bash ==> older one

change it to as follow
Question: How do i give a normal user root-privileges?
Bad advice:

Assign user-id 0 to it. (Of all the stupid advice, this is probably the worst.)
Good advice:

DON'T! This will not give root-privileges to the user. It will make the user root, or rather an alias for root. It is not the name "root" that is special. The superuser is the user with user-id 0. And if you're going to run as root all the time (which is a fucking stupid thing to do), just log in as root instead. This way you won't have a "hidden" alias for root lying around. If a normal user needs root-privileges, use sudo(8). If you just need root-privileges temporarily, use su(1).
Old 01-08-2006, 08:06 PM   #18
LQ Newbie
Registered: Nov 2005
Distribution: OpenSuSE 10.0
Posts: 11

Rep: Reputation: 0
I tried that gilead, and it didn't change a thing for some reason. I think what I want to do is just move everything off of the hard disk and reformat it into a linux file system. This should also prevent any future problems along the same lines. And it should be simple... I'll just transfer all my music onto my main harddrive, reformat the other one, and then transfer it back. Note I said it should be... next will come a post telling me how it's not going to be that simple LoL.
Old 01-08-2006, 09:31 PM   #19
Senior Member
Registered: Dec 2005
Location: Brisbane, Australia
Distribution: Slackware64 14.0
Posts: 4,138

Rep: Reputation: 166Reputation: 166
Yep - should is one of my favourite words too Good luck!
Old 01-09-2006, 12:14 AM   #20
LQ Newbie
Registered: Nov 2005
Distribution: OpenSuSE 10.0
Posts: 11

Rep: Reputation: 0
Well, everything appears to be perfect now. My wife can edit her files from her computer, and that's the only folder I gave 'others' rwx permissions on (except for an empty folder I'm using to bypass networking problems, but that's another story). So thanks!!! to everyone who posted to help me out, and especially to gilead for being patient and helping me narrow down options and get to the root (ha ha) of the problem. Altho one last question: since anyone has access to those mp3's in her folder, could a person somehow use an mp3 to gain access to my system through a media program such as amaroK? And if so, could I protect against this by giving the user "nobody" (which is what my wife's laptop connects as through Samba) those permissions instead of everyone, or does "nobody" simply refer to any computer accessing mine? Or could people even access my computer like that since they aren't on my home network? Kind of a wordy question, but I hope my meaning got through...
Old 01-09-2006, 11:04 AM   #21
Senior Member
Registered: Jun 2004
Distribution: Arch, Debian, Slack
Posts: 1,016

Rep: Reputation: 47
i don't think anyone could "use" an mp3 to gain access to your system, but the point of having proper permissions is that if anyone -did- gain access, they could trash any files they had write permissions to, in this case your mp3s. they could also use the directory to write stuff to, which probably isn't a good idea.

again, you should set up a group for anyone who uses the mp3s and directory, and give only them permissions (plus the owner, obviously, which would most likely be you). you should also secure the directory through your smb.conf with user share level security (man smb.conf, man smbpasswd).

afaik, "nobody" is a system account sometimes used for running certain applications or daemons (web servers, etc.) doing a quick google, i see that it also has some other more specific purpose related to root and NFS, so it seems that in any case it really shouldn't be used as a regular user account. gl


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
file permissions OK, but command permissions? stabu Linux - General 2 10-05-2005 01:00 PM
permission ... permissions .... permissions alaios Linux - General 1 05-31-2005 05:16 AM
getting a directory's permissions and creating a new one with the same permissions newbie1000101 Programming 1 04-10-2004 01:52 PM
permissions JROCK1980 Linux - Software 6 04-09-2004 05:03 AM
need help with permissions hbbtstar Linux - Newbie 4 10-13-2003 07:02 AM > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 11:59 AM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration