Slackware This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
 |
|
03-16-2006, 11:58 PM
|
#1
|
Member
Registered: Jan 2006
Location: Vulcan
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
Here is fstab:
/dev/hde6 swap swap defaults 0 0
/dev/hde7 / reiserfs defaults 1 1
/dev/hde1 /mnt/hde1 ntfs ro 1 0
/dev/hde5 /mnt/hde5 ntfs auto,user,umask=222 1 0
/dev/cdrom /mnt/cdrom auto noauto,user,ro 0 0
/dev/hdd /mnt/cdrom1 auto noauto,user,ro 0 0
/dev/fd0 /mnt/floppy auto noauto,user 0 0
/dev/sda /mnt/usb auto noauto,user 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
proc /proc proc defaults 0 0
First time, so maybe I did something wrong. I was just trying to read off of hde5. Maybe I wrote it wrong. It didn't work at all when it was just ro.
Any help would be appreciated. Sorry if I left out any info.
|
|
|
03-17-2006, 12:40 AM
|
#2
|
Senior Member
Registered: Nov 2003
Location: Perth, Western Australia
Distribution: Ubuntu, Debian, Various using VMWare
Posts: 2,088
Rep:
|
Is it /dev/hde1 or /dev/hde5 that you are having problems with. If it is hde1, try adding user after the ro flag, like for hde5.
Does it work as root? Without the "user" flag, it won't work for a user
I hope this helps
--Ian
|
|
|
03-17-2006, 01:01 AM
|
#3
|
Member
Registered: Jan 2006
Location: Vulcan
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.
Thanks!
|
|
|
03-17-2006, 01:15 AM
|
#4
|
Member
Registered: Mar 2005
Location: chennai(madras), India
Distribution: slackware ofcourse
Posts: 654
Rep:
|
/dev/hde5 /mnt/hde5 ntfs auto,rw,umask=000 1 0
before "rw "option
which kernel u r using? and is the modules loaded for ntfs read/write support?
(some "captive ntfs" is there)
|
|
|
03-17-2006, 01:27 AM
|
#5
|
Member
Registered: Jan 2006
Location: Vulcan
Distribution: *buntu - Slackware - Anything on USB
Posts: 254
Original Poster
Rep:
|
It was the test kernel on the CD. 2.6.13
I just chose test26.s when I installed. Then upgradepkg *.tgz from the linux-2.6.13 directory on CD 2. I honestly don't know about the ntfs module.
I will try:
/dev/hde5 /mnt/hde5 ntfs auto,rw,umask=000 1 0
I will post back. Thank you.
|
|
|
03-17-2006, 01:47 AM
|
#6
|
Member
Registered: Jan 2006
Location: Vulcan
Distribution: *buntu - Slackware - Anything on USB
Posts: 254
Original Poster
Rep:
|
That did the trick. I can access the drive, I can see the files, AND I can access the files as well.
I sure would like to make user access read and execute only, though. I would like to limit write access to root only. Is this possible?
Do I change umask=000 to something else to do this?
Thanks again!
|
|
|
03-17-2006, 06:10 AM
|
#7
|
Member
Registered: Mar 2005
Location: chennai(madras), India
Distribution: slackware ofcourse
Posts: 654
Rep:
|
Quote:
Do I change umask=000 to something else to do this?
|
may b i am not sure abot this thing
Quote:
I honestly don't know about the ntfs module.
|
"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 
Last edited by rkrishna; 03-17-2006 at 06:14 AM.
|
|
|
03-17-2006, 06:49 AM
|
#8
|
Senior Member
Registered: Apr 2003
Location: Germany
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,640
Rep: 
|
umask works with the inverse of the values of "chmod", thus umask=000 means the same as chmod 777 *, "man fstab" for details. HTH.
|
|
|
03-17-2006, 08:26 AM
|
#9
|
Member
Registered: Jan 2006
Location: Vulcan
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.
Thanks everyone
|
|
|
03-17-2006, 09:03 AM
|
#10
|
Senior Member
Registered: Apr 2003
Location: Germany
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,640
Rep: 
|
You might still want to change that to
/dev/hde5 /mnt/hde5 ntfs user,auto,rw,umask=222 0 0
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.
|
|
|
03-17-2006, 09:46 AM
|
#11
|
Member
Registered: Jan 2006
Location: Vulcan
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.
/dev/hde5 /mnt/hde5 ntfs user,auto,rw,umask=222 0 0
or
/dev/hde5 /mnt/hde5 ntfs user,auto,ro,umask=222 0 0
One way to find out!
|
|
|
03-17-2006, 11:19 AM
|
#12
|
Member
Registered: Nov 2004
Location: Virginia, US
Distribution: Slackware 14.1 multilib
Posts: 149
Rep:
|
Quote:
Originally Posted by DrEwMoNeY
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.
/dev/hde5 /mnt/hde5 ntfs user,auto,rw,umask=222 0 0
or
/dev/hde5 /mnt/hde5 ntfs user,auto,ro,umask=222 0 0
One way to find out!
|
The line that I use in my fstab to get to my NTFS partition is...
Code:
/dev/hda1 /mnt/windows ntfs noauto,owner,umask=022,users,noexec,nodev,ro 1 0
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
Hope this helps!
|
|
|
03-17-2006, 11:58 AM
|
#13
|
Member
Registered: Jan 2006
Location: Vulcan
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:
dr-xr-xr-x
This is what I would like for hde5. I will try:
/dev/hde5 /mnt/hde5 ntfs noauto,owner,umask=022,users,noexec,nodev,ro 1 0
Thank you.
Last edited by DrEwMoNeY; 03-17-2006 at 02:03 PM.
|
|
|
03-17-2006, 01:37 PM
|
#14
|
Member
Registered: Jan 2006
Location: Vulcan
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:
dr-xr-xr-x
Thank you everyone!
Last edited by DrEwMoNeY; 03-17-2006 at 02:02 PM.
|
|
|
03-17-2006, 02:42 PM
|
#15
|
Senior Member
Registered: Oct 2005
Distribution: Slackware 14.1
Posts: 3,482
|
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:
# # # Windows NT4 partitions # # #
/dev/hda2 /mnt/nt_c1 ntfs noauto,users,ro,exec,umask=0222 0 0
/dev/hda3 /mnt/nt_c2 ntfs noauto,users,ro,exec,umask=0222 0 0
/dev/hda6 /mnt/nt_d ntfs ro,exec,umask=0222 0 0
/dev/hda7 /mnt/nt_e ntfs ro,exec,umask=0222 0 0
/dev/hda8 /mnt/nt_k ntfs noauto,users,ro,exec,umask=0222 0 0
/dev/hda9 /mnt/nt_l ntfs noauto,users,ro,exec,umask=0222 0 0
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.
I hope this helps.
|
|
|
All times are GMT -5. The time now is 01:40 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|