On Apr 10 19:00, Steven Penny wrote:
> On Fri, Apr 10, 2015 at 5:07 AM, Corinna Vinschen wrote:
> > Please give the new code a try.  I uploaded new 2015-04-10 developer
> > snapshots to https://cygwin.com/snapshots/
> 
> Here is the test I ran:
> 
>     $ cd /cygdrive/c
> 
>     $ touch ~/{alpha,bravo}.sh ~+/{charlie,delta}.sh
> 
>     $ chmod +x ~/bravo.sh ~+/delta.sh
> 
>     $ ls -l --color ~/{alpha,bravo}.sh ~+/{charlie,delta}.sh
>     -rw-rw-r--+ 1 John None 0 Apr 10 16:51 /cygdrive/c/charlie.sh
>     -rwxrwxr-x+ 1 John None 0 Apr 10 16:51 /cygdrive/c/delta.sh    (green)
>     -rw-r--r--  1 John None 0 Apr 10 16:51 /home/John/alpha.sh
>     -rwxrwxr-x  1 John None 0 Apr 10 16:51 /home/John/bravo.sh     (green)
> 
> So "charlie.sh" looks strange because it has that extra write permission.
> However this is not a big deal for me. My concern was that everything was
> showing up executable (green) when running "ls --color". So overall this is an
> improvement, thanks.

What is '~+'?  Is that some weird bash feature?

Did you check the ACL?  The ACL before and after the change should
explain what happened.  Check it with getfacl *and* icacls to get
an idea what it looks like, and compare the result with the POSIX
ACL rules, as outlined on, e.g., http://linux.die.net/man/5/acl.


Corinna

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