"id; touch newfile; stat newfile"
OK, you are right "-o permissions" alone accurately preserves owners and
permissions, which is sort of what I needed. I was confused by some
experiments I did with memory sticks accessed from Windows.
"Yes, that should be expected. You cannot both define the owne
"At the moment, it seems that mount.ntfs-3g disables -o permissions if -o
uid=UUU and/or uid=GGG are also specified."
Yes, that should be expected. You cannot both define the owner of a file both
as the current user and a forced user. See
http://www.tuxera.com/community/ntfs-3g-advanced/ownershi
Note, my shell log shows the behavior with mount -o
uid=500,gid=500,umask=000. The same behavior (chmod has no effect)
occurs when using mount -o permissions,uid=500,gid=500,umask=000 (as if
-o permissions is being silently ignored).
--
You received this bug notification because you are a member
