On Thu, May 19, 2005 at 06:48:05PM -0300, André Melo Carvalhais Dutra wrote: > I 'm having a very odd behaviour using mount, and I think it is > possibly a bug, but since I'm not an experienced linux user, I'd like > to post the issue here first just to be asured I'm missing nothing, > before reporting it to bts. > I'm running a few weeks old snapshot of Sarge (never updated), > kernel 2.6.2-686 (from the install CD) and mount version 2.12-10 (also > from the CD). What I'm really trying to do, is to give all users on a > given group permission to access mounted volumes, so I created a group > called 'access' (gid 20000), and put some users and root into it. I > added to following line in fstab to get the partition mounted every > boot: > /dev/hda1 /mnt/win ntfs defaults,uid=0,gid=20000,umask=227 0 0 > What does happen is that the partition get mounted, but with the > wrong umask (trying umask=227 mounts it umask=363, trying umask=337 > mounts it umask=723, and so on).
I dimly remember we had a thread on a similar issue a while back, but I can't find it right now... Anyway, the solution was to put a zero in front of the octal value, i.e. umask=0227 -- apparently, filesystem types differ in how they handle options. BTW, that's always a good default strategy, if something is weird with permissions... :) Cheers, Almut -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
