It seems that the UDF filesystem ignores the gid uid and umask mount
options and uses the values in the filesystem instead. I searched
around and found a bug reported to debian last year about this, but it
was never resolved.
Going by what that bug says, if you create a udf filesystem without rock
ridge extensions with mkisofs -udf, then the kernel accepts the uid,
gid, and umask options, but with rock ridge extensions, it ignores those
options. I have been messing around with using the packet writing
interface and mkudffs to set up a read/write udf filesystem on a cdrw
and I ran into this problem because my non root account can't access the
disk.
It is nice that UDF is capable of storing the permissions on disk, but
when values are specified on the mount options, they should override
those on the disk. For removable media using the stored uid and gid on
the disk is detrimental because they aren't going to have the correct
meaning when you insert the media into another computer, so it is
important to be able to override them.
Am I correct in thinking this is a bug, or is there already a workaround
I haven't found?
P.S. Please CC me on replies as I am not subscribed to the list ( would
blow my pop quota )