Around about 09/07/2003 03:57, Gordon Messmer typed ...>
/dev/hda1 /mnt/windows vfat uid=nobody,gid=windows,umask=002 0 0
This will mount the directory so that all files and directories are owned by "nobody", group "windows", and permissions of 0775.
I think that's essentuially what I have, and it's fine for those files that are *there*, but I find it interferes with newly created files - try touching a file and checking it's perms.
# mount vfat.fs /mnt/floppy/ -o loop,uid=nobody,gid=gordon,umask=002 \ -t vfat
[gordon@xxxxxxxxxx:~]$ touch /mnt/floppy/test1 [gordon@xxxxxxxxxx:~]$ ls -l /mnt/floppy total 0 -rwxrwxr-x 1 nobody gordon 0 Jul 16 13:35 test1*
As expected, the file is mode 0775.
With my set up, it's created with group perms of read only (i.e., it's set the FAT32 read-only bit).
When the FAT32 read-only bit is set, the file's mode will be 555. FAT doesn't have different permissions for UID/GID, so I don't know what you're seeing. How about you tell us what's in /etc/mtab for your FAT FS?
I can only assume it's something odd to do with me not being 'nobody', and it only using the user perms to map to the freshly created 'read-only' bit. Maybe.
Probably not. The options I suggested work here.
-- Shrike-list mailing list Shrike-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/shrike-list
