I noticed fmask=0000 in vfat_opts line of /etc/default/mount-opts. (and umask=0000 for ntfs_opts)

Out of curiosity, why do we want to have every and each file on vfat/ntfs marked as 'executable' on birth?* Wouldn't something like fmask=0133 be more sane, for both vfat and ntfs?

*In linux filesystems, umask=0000 results in 0666 permissions for files and 0777 permissions for directories, respectively, on birth. For windows filesystems (vfat and ntfs) mounted under linux, it results in 0777 for *both* directories and files, making every single file executable at the very moment of its creation.

That's why it's better to use fmask than umask for vfat/ntfs, and it shouldn't be 0000, unless we explictly want to make everything rwx.

/Estel