On Jan 28 15:24, Rainer Blome wrote:
> (Apologies for not using the reply feature, I was not
> subscribed when the last mail was sent. I am now subscribed.)

The "In-Reply-To" is still missing in your mails, so you're invariably
breaking threading.  T'would be nice if you could make your mailer
behave :)

> > Corinna Vinschen wrote:
> > On Jan 28 01:27, Christopher Cobb wrote:
> >> Or maybe chmod is broken, like it is on my machine:
> >> $ chmod 777 x
> >> chmod: changing permissions of âxâ: Invalid argument
> 
> > Can you please send the icacls output of the current directory and
> > the icacls out for the file x?
> 
> Here are the icacls outputs for the test case:
> 
> $ umask
> 0027
> 
> $ mkdir bar
> $ cd bar
> $ icacls .
> . hostname\username:(I)(OI)(CI)(F)

This... doesn't look like an ACL created by Cygwin.  If you're running
Cygwin 2.4.1, the acl should always at least contain ACEs for the
default POSIX perms, plus a NULL ACE:

foo NULL SID:(DENY)(Rc,S)
    VINSCHEN\corinna:(R,W,D,WDAC,WO)
    VINSCHEN\vinschen:(R)
    Everyone:(Rc,S,RA)

For directories also inheritable default perms for "CREATOR OWNER" and
"CREATOR GROUP".  Is that really a Cygwin mkdir?!?  And then, what about
this unknwon group with gid 213?  What does

  $ getent group 213

print?  Something's weird here...


Thanks,
Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat