FedoraThis forum is for the discussion of the Fedora Project.
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 have an external hard drive(ntfs) and I can only access it through root. I tried changing the permissions(chmod 777 Backup(name of the drive)) It claims it is succesfully changed but permissions when I check are still set to 500. when I try to change permissions through gui it says I can't change permissions on a read-only disk(because it is ntfs). Buuut, I never set permissions to root on the drive to begin with. What is going on? It is a removable disk and this shouldn't happen. Driving me crazy. Recommendations?
You probably won't be able to get 777 as your permissions. Since it is NTFS you'll probably just get 555 (which is read and execute for all) unless you are using one of the projects that allows full NTFS reading.
For non-linux file systems, you can't use the chmod command on the mounted partition. Instead, the same information needs to be included in the mount command. Read the man mount before selecting the options that you want to use.
You can for instance, make yourself the owner (user) of the partition with the uid= options. So if your user number is 501, then using the option 'uid=501' will give you access. Also setting the group ownership with the 'gid=' option will allow you to control who may read files on the drive.
Because linux doesn't normally have write support for NTFS drives, using the 'fmask=' option for regular files and the 'dmask' option for directories makes more sense then using the 'file creation mask' since you won't be creating files on this parition in linux.
One final thing I should mention about the 'uid' and 'gid' options. You can use your username and groupname respectively. So if your userID is 501 and your username is 'beatupbilly', then the options: uid=beatupbilly,gid=users will make you the owner of the partition, and the group ownership is assigned to the 'users' group. This is what you would do instead of using the command chown beatupbilly:users /media/Backup.
Maybe you can help me understand this problem: unless I am logged in as roon, even though I specify the username there directories on my Mac's Samba shares that can't be read or written. Only resources with "other" permissions can be read or written on the Mac.
I strongly suspect the following is the reason: while the username is the same on both machines, my primary username = UID 1000 in Knoppix (hard drive installed) but UID 501 on the Mac! I think that when I am logged in as root in KNoppix this distinction doesn't matter, but when when I am in the user account, the Knoppix PC isn't concerned that the username is the same on the Mac's files, it looks at the numeric UID and bases its permissions on that. But shouldn't it ignore the Mac's file permissions? Despite my having dmask=777 and fmask=777 in the fstab entry the Mac's directory permissions seem to govern. Any ideas as to why my dmask and fmask aren't working? I also tried umask=000 in a shell script and encountered the same problem.