SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Distribution: *buntu - Slackware - Anything on USB
Posts: 254
Rep:
Another FSTAB Victim
I've read quite a few posts just to get this far. Sorry if this same scenario has come up before.
I finally got my NTFS partitions mounted as a user other than root, and I got the permissions changed, so I could view what was on them. All I want is to be able to have a user read off them. I don't need to write to them, just view photos etc.
I finally got it to work, where it would actually let me view files. But when I clicked on a picture, it showed an empty browser (in Konqueror). When I clicked back, all the permissions had mysteriously changed back. Every file had the little lock on it. I even checked the permission beforehand, from the command line: ls -l
Distribution: *buntu - Slackware - Anything on USB
Posts: 254
Original Poster
Rep:
Yeah, when I'm logged in as root, no problem. Hde1 actually has XP on it. That is why I'm just trying to get read access for hde5. It is basically a data partition.
I've had to ween myself from logging in as root. Unfortunately, adding a user causes other problems. I've just been working them out, one at a time.
I'm guessing something is wrong in the hde5 line. Just not sure what it is.
It used to read:
/dev/hde5 /mnt/hde5 ntfs ro 1 0
I couldn't even access the partition then. Now I can access it, but nothing in it. I can see the files in it, I just can't open or view them. I'm pretty sure I need read and execute.
I think I set it all users read and execute hde5, as root. Everything was okay until I actually tried to view a picture. Every file on the drive locked up on me.
Distribution: *buntu - Slackware - Anything on USB
Posts: 254
Original Poster
Rep:
Quote:
Originally Posted by rkrishna
may b i am not sure abot this thing "lsmod" will list the modules, since u installed that package(module) from second cd it wil automatically load that why u could access the drive hi
Okay, lsmod. I always forget, I don't use that one too much. Thanks, that makes sense that it was loaded because I had root access. Thank you.
Quote:
Originally Posted by JZL240I-U
umask works with the inverse of the values of "chmod", thus umask=000 means the same as chmod 777 *, "man fstab" for details. HTH.
Thanks, I started out with this:
/dev/hde5 /mnt/hde5 ntfs auto,user,umask=222 1 0
and then ended up with this:
/dev/hde5 /mnt/hde5 ntfs auto,rw,umask=000 1 0
maybe I need to really do this:
/dev/hde5 /mnt/hde5 ntfs auto,rw,umask=222 1 0
I originally had umask=222 (first post), but not rw. It just seemed like a bit of a contradiction to me. But what I had originally didn't work, so maybe I will try that.
but I'm not sure whether that is users (doing this from memory...). Maybe you can delete the "rw" tag then or rather change it to "ro" -- just to make sure.
Distribution: *buntu - Slackware - Anything on USB
Posts: 254
Original Poster
Rep:
I think the very first change I made to it was adding user. When I installed I think it looked like this:
/dev/hde5 /mnt/hde5 ntfs ro 1 0
So I added user so it said user,ro. That didn't seem to help. That is when I went to auto,user,umask=222.
Making it read-only across the board (root also) is actually preferable. I will try what you said.
Both being 0 at the end seems right to. Not sure if I want to leave dump/fsck up to Linux. Only because it is a NTFS partition. Linux might try to eat it just for spite.
I think the very first change I made to it was adding user. When I installed I think it looked like this:
/dev/hde5 /mnt/hde5 ntfs ro 1 0
So I added user so it said user,ro. That didn't seem to help. That is when I went to auto,user,umask=222.
Making it read-only across the board (root also) is actually preferable. I will try what you said.
Both being 0 at the end seems right to. Not sure if I want to leave dump/fsck up to Linux. Only because it is a NTFS partition. Linux might try to eat it just for spite.
and so far I have never had any problems accessing any of the files on that partition. If you need explanations on the different options that I'm using go to http://www.die.net/doc/linux/man/man8/mount.8.html
Distribution: *buntu - Slackware - Anything on USB
Posts: 254
Original Poster
Rep:
Every other combination I tried except for:
/dev/hde5 /mnt/hde5 ntfs auto,rw,umask=000 1 0
failed to let me have access. I tried combinations of auto,ro,umask=000 and auto,user,rw,umask=000 and many others. I tried to write it every way possible. I finally tried just umask=000. No luck!
From my first post:
/dev/hde7 / reiserfs defaults 1 1
This partition boots with the permissions set the way I would like them to be set for hde5. When I log in as user it is set as:
Distribution: *buntu - Slackware - Anything on USB
Posts: 254
Original Poster
Rep:
Still no access. I guess I'll just go back to the first one that worked. I just hate to have user write access on my NTFS partition!!!
BIG EDIT:
This seems to work:
/dev/hde5 /mnt/hde5 ntfs auto,ro,umask=000 1 0
I would almost swear I tried the same except with 0 0 at the end. Maybe that was the difference. Anybody wan't to explain that one? At least it gave me what I was looking for. Logged in as a user, I get:
I have several NTFS partitions on my disk. I have no problems with mortal user accounts accessing the partitions and the partitions are mounted read-only. Here are my fstab entries:
I mount some of the partitions with noauto because I seldom access those partitions on a regular basis. The other partitions I access every time I boot into Slack.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.