On Jul 18 09:34, Corinna Vinschen wrote: > On Jul 17 18:18, Eric Blake wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > According to Corinna Vinschen on 7/17/2008 9:55 AM: > > | Hi, > > | > > | again I would like to encourage the Cygwin maintainers, to try the new > > | Cygwin 1.7.0 release and to look for problems in their packages which > > | might be a result of the fairly massive changes in Cygwin 1.7. I > > | attached a list of the changes below. The latest changes are: > > | > > | - Changes in mkpasswd/mkgroup and in seteuid() should result in more > > | correct user tokens in AD domains. Try the LSA module. > > | - Case-sensitivity on NTFS and NFS and mount option "posix=[0|1]". > > | - Remove CYGWIN=ntsec and CYGWIN=smbntsec options in favor of a mount > > | option "acl"/"noacl". > > > > Somewhere between setting obcaseinsensitive to 0 yesterday and upgrading > > to the new cygwin1.dll today, I'm now suffering from an inability to > > modify files on a shared drive on my work machine. I can create empty > > files and remove existing files just fine, but get access denied on any > > attempt to change contents. The -1 for owner and group looks fishy as > > well. > > Drive U is apparently a Samba drive. Is that in a Windows domain? > If not, try the noacl mount option. It's equivalent to what was > CYGWIN=nosmbntsec before.
Hmm, I can reproduce it and now that I see it myself I can see how this is a problem with cygdrive mounts. I assume the best way to handle this would be to set Samba drives to noacl by default, right? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat