'umask' and mounting of vfat filesystem.

From: Daniel M. (xt_at_nm.ru)
Date: 08/17/04

  • Next message: Paul Gear: "Re: Sarge RAID install" 
    To: debian-user@lists.debian.org
Date: Mon, 16 Aug 2004 23:43:09 -0700

    Hello everybody,

    According to the man page for 'mount', 'umask=value' is used as follows:

    "umask=value
                  Set the umask (the bitmask of the permissions that are not
                  present). The default is the umask of the current process. The
                  value is given in octal."

    But somehow I don't succeed in getting that behavior. For example,
    if I set 'umask=0000', I am supposed to get '-rwxrwxrwx' permissions.
    But some files/directories have '-r-xr-xr-x' permissions (for example,
    in the root directory of vfat's filesystem those files are: msdos.sys,
    ntdetect.com, ntldr, io.sys, 'Program Files'. There are other (non-system)
    files, deeper in the directory structure, which also get those incorrect
    permissions).

    Here is a list of umask's values and permissions those files are actually
    getting ('correct' means that they are getting the same permissions as all
    the other files):

    umask=0000: -r-xr-xr-x
    umask=0111: -r--r--r--
    umask=0222: correct
    umask=0333: correct
    umask=0444: ---x--x--x
    umask=0555: ----------
    umask=0666: correct
    umask=0777: correct

    Why those (and many other) files are different and don't get the correct
    permissions specified by 'umask' option?

    Another question: my shell process's file creation mask is '0022',
    which means that if 'umask' option is not used in 'mount' command
    when mounting vfat filesystem, the default permissions would be
    '-rwxr-xr-x'. But the actual permissions I get are: '-rwxr--r--'
    (the files mentioned above once again get different permissions:
    '-r-xr--r--'). Why is that so?

    Daniel. 

    -- 
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
  • Next message: Paul Gear: "Re: Sarge RAID install"

    Relevant Pages

    • Re: rw vs. umask in mount call, also, conditional mounting
      ... The 'rw' option is something passed to the mount command that tells it ... The umask basically sets up the 'default' permissions set that will be ... > I have a usb card reader that when plugged into my system is either ...
      (comp.os.linux.setup)
    • Re: File permissions help!
      ... umask specifies the umask for everyfile of the mounted vfat file system. ... If you don't mind anyone being able to write, use "umask=0" (which will set all permissions to rwxrwxrwx). ... Alternatively, you could change the mount options to allow any user to mount the filesystem, in which case I think the files'll be under their uid and they'll be the owner. ...
      (uk.comp.os.linux)
    • Re: writeprotection of unmounted mountpoints automaitcally - possible??
      ... >>options should change the permissions. ... Changing the mount point options does not affect the mount ... root can still write to the raw device, ... will be usable by the regular user, but the directory will not be ...
      (Fedora)
    • Re: [RFC] FUSE permission modell (Was: fuse review bits)
      ... > 2) Suid and device semantics should be disabled within the mount ... I can see plenty of uses where I want a filesystem generated by ... permissions model - which will break some programs? ... For most virtual filesystems, the "remote" information does not map to ...
      (Linux-Kernel)
    • Re: R/W access of a vfat partition by any user ?
      ... FAT32 partition will be writable by any user instead of just root. ... users Allow every user to mount and unmount the file system. ... The 'umask=022' makes all files and directories have rwxr-xr-x permissions. ... If you want different perms and you don't speak binary, ...
      (alt.os.linux.suse)