🚀 go-pugleaf

g@Elizabeth.netcraft.com.au (Geoffrey D. Bennett) writes:

> Manfred Bartz (mbartz@werple.net.au) wrote:
> : MS-VFAT does not support file permissions etc...
> 
> : You can mount a partition ``suid'' if you want to give permissions to
> : anyone who mounts the drive.
> 
> Don't you mean the 'umask' option?  suid means "Allow
> set-user-identifier or set-group-identifier bits to take effect."
> which is irrelevant since MS-VFAT does not support file permissions.

You are right.  What I wanted to achieve was that if a particular user
mounts the DOS drive, all files are owned by that user.  It turns out
that ``suid'' doesn't do anything.

> I do it like this:
> /dev/sdb1             /dos         msdos   umask=0 0 0
> 
> Or if you want to restrict access to certain users, create a group for
> them and use the gid option:
> /dev/sdb1             /dos         msdos   gid=70,umask=07 0 0

Very good.  I just took your example and implemented that.  :-)
So, the umask is the inverse of the permissions as used in chmod?

While on that topic, for the ext2-fs, I just discovered that I can
change my umask for the current session with umask -S mmm; very
useful.  UNIX (Linux) never ceases to amaze me!   :-)

> I don't see any point in using "user,noauto" for nonremovable media?

I use those partitions irregularly, unmounting them allows kerneld to
unload the VFAT and FAT support modules.  

> : All this is covered in the manpage for ``fstab''.
> 
> And 'mount'.
> 
> : I use a test editor to change ``fstab''. 
> : Challenge: Try doing this with the Redhat tools.  Is that possible?  Anyone?
> 
> Yes it is.

Surprise!  I couldn't figure it out when I tried Redhat V3.  

-- 
Manfred Bartz <mbartz@werple.net.au>
  --- LINUX, live free or die ---