getting fat32 (Win98SE) part to mount with dmask and fmask options
Please refer to the following link for history:
My thanks to those who have wrestled with this problem in the Red Hat forum. This thread has turned away from being Red Hat specific and is more about windows (in linux) and so has become more suitable for the general forum. So here I am...
I am trying to get a windows fat32 partition to automount with permissions set to -rwxrw---- and drwxrw---- (read/write access for the logged in user - execute access only for directories and root). I have attempted this (via mount command - ultimately this will be an fstab entry - by the following (amongst many permutations):
(I do not want any bits set for "others", and I want rw- not r-x for user...)
This is a RH9 machine running dual-boot with Win98SE 4.44. The Win98 disk was resized with fips. I note that the partition was not originally fat32 - it was originally fat16 and it has a utility for changing the fs to fat32 which says it has been run. (I have yet to see a win98 machine without this tho).
The users are all members of the "users" group.
The above mount options work when mounting a memory stick, and also when mounting a vfat partition. So what is so special about the win98 partition?
I can give users rw access using the umask option, but I also have to set the last bit (x access) so the directories will work. Naturally, I'm not too keen on users running executables on the win32 partition.
I have the following intellegence to impart:
The above commands were run under the 2.4.20-6 kernel.
Apparently the 2.4 series kernels do not support dmask and fmask options.
The other tests were done under the 2.6.10 kernel (on another machine which is a dedicated linux box!) and so introduced confusion.
I guessed (wrongly) that if the man page exists then the feature must be supported. Silly me!
This leaves only to discover why the rw option fails to mount read-write only as advertised.
I could be wrong, but I think the umask would be safe with the execute bit set, if you were to use the noexec option. This should stop execution of binaries anyway. I don't know about scripts. It may be worth playing with.
The rw mount option just designates whether or not you can write to the device at all. It doesn't do anything with file permissions (unless you're suggesting that you don't have write access).
mount -t vfat /dev/hda1 /mnt/win98 -o umask=000 noexec
That may just do the trick. Unfortunately the machine in question has left my clammy clutches. I'll have to stick a linux partition on my remaining win98 machine to test this out.
(The mount command shown in the first post gives write access only to root.)
|All times are GMT -5. The time now is 12:39 PM.|