On Wed, 31 Dec 2008, Michael Goetze wrote:
Package: libfuse2
Version: 2.7.4-1.1
When mounting something with curlftpfs 0.9.1-3+b2 and passing -o
uid=1000,umask=077 to libfuse2, I can only see files of mode 700. If I
only pass -o uid=1000, I get lots of files with modes like 644, i.e.
if you actually applied a umask of 077 to these they would be 600, not 700.
Hmm. I'm not sure what the original intention was, but I think it may
have been what the current behavior is. The short description of the
option in the help output is:
-o umask=M set file permissions (octal)
and the long description in the README:
umask=M
Override the permission bits in 'st_mode' set by the filesystem.
The resulting permission bits are the ones missing from the given
umask value. The value is given in octal representation.
Both seem to imply that the original file mode is ignored. Yes this
is inconsistent with the normal notion of umask, and the option
should've perhaps been called mode (and bits reversed). But now I'm
inclined to leave things as is, otherwise filesystems could break.
Thanks,
Miklos
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
