Re: Nasty permissions / pathing bug on 1.7

[Corinna Vinschen <corinna-cygwin at cygwin dot com>]

On Dec  1 17:42, Dave Korn wrote:
> Steven Hartland wrote:
> > Just to be 100% clear its not the fact that the script errors, its the fact
> >  that the permissions after the initial DOS pathed chmod doesn't actually 
> > set the permissions correctly and doesn't throw any error.
> 
>   Also, it's not just perl, you can reproduce it in a shell:
> 
> > $ ls -l /tmp/test.exe
> > ls: cannot access /tmp/test.exe: No such file or directory
> > 
> > $ touch /tmp/test.exe
> > 
> > $ ls -l /tmp/test.exe
> > -rw-r--r-- 1 DKAdmin None 0 2009-12-01 17:36 /tmp/test.exe
> > 
> > $ cygpath -w /tmp/test.exe
> > F:\cygwin-1.7\tmp\test.exe
> > 
> > $ chmod 777 'F:/cygwin-1.7/tmp/test.exe'
> > 
> > $ echo $?
> > 0

That's by design.  When you use Win32 paths, instead of POSIX paths,
you will get Win32 default permission handling.  Or, in other words,
for all DOS paths the mount mode is "noacl".


Corinna

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

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple