Re: Execute permission not set when creating files

2008-10-29 Thread John Cooper
Matthew Woehlke wrote: > Does adding a+x really fix the problem? If so that seems... surprising. Also surprising is that the problem no longer occurs today. When I create a file using `ls > b.txt', I *can* now read it on my wife's desktop (and it just has the default permissions -rw-r--r--). So

Re: Execute permission not set when creating files

2008-10-28 Thread Matthew Woehlke
John Cooper wrote: Matthew Woehlke wrote: I don't think I've met a POSIX-like system yet that automatically creates things with any +x bits set. I'm assuming that the recent Cygwin's failure to set the +x bit is the cause of the underlying problem, namely that any files I create (e.g., via out

Re: Execute permission not set when creating files

2008-10-28 Thread Larry Hall (Cygwin)
John Cooper wrote: Matthew Woehlke wrote: > I don't think I've met a POSIX-like system yet that automatically creates things with any +x bits set. I'm assuming that the recent Cygwin's failure to set the +x bit is the cause of the underlying problem, namely that any files I create (e.g., via o

Re: Execute permission not set when creating files

2008-10-28 Thread Christopher Faylor
On Tue, Oct 28, 2008 at 10:15:45PM -, John Cooper wrote: >Christopher Faylor wrote: >>Are you sure you're using the cygwin version of all utilities? You >>seem to have some duplication between c:\cygwin\bin and c:\bin. > >I have a custom version of `ls' in the bin directly, but it's >definitel

Re: Execute permission not set when creating files

2008-10-28 Thread John Cooper
Matthew Woehlke wrote: > I don't think I've met a POSIX-like system yet that automatically creates things with any +x bits set. I'm assuming that the recent Cygwin's failure to set the +x bit is the cause of the underlying problem, namely that any files I create (e.g., via output redirection) ca

Re: Execute permission not set when creating files

2008-10-28 Thread Matthew Woehlke
John Cooper wrote: I've just upgraded to the latest version of Cygwin (1.5.25-15) and found that the execute bit is not getting set when I create files: $ umask 'u=rwx,g=r,o=r' $ touch a $ ls -l a -rw-r--r-- 1 John None 0 Oct 28 21:42 a (the execute permission also doesn't get set when I use th

Re: Execute permission not set when creating files

2008-10-28 Thread John Cooper
Christopher Faylor wrote: > Are you sure you're using the cygwin version of all utilities? You seem to > have some duplication between c:\cygwin\bin and c:\bin. I have a custom version of `ls' in the bin directly, but it's definitely the Cygwin version of `touch'. I also get the same problem

Re: Execute permission not set when creating files

2008-10-28 Thread Christopher Faylor
On Tue, Oct 28, 2008 at 09:55:08PM -, John Cooper wrote: >I've just upgraded to the latest version of Cygwin (1.5.25-15) and found >that the execute bit is not getting set when I create files: > >$ umask 'u=rwx,g=r,o=r' >$ touch a >$ ls -l a >-rw-r--r-- 1 John None 0 Oct 28 21:42 a > >(the exec

Execute permission not set when creating files

2008-10-28 Thread John Cooper
I've just upgraded to the latest version of Cygwin (1.5.25-15) and found that the execute bit is not getting set when I create files: $ umask 'u=rwx,g=r,o=r' $ touch a $ ls -l a -rw-r--r-- 1 John None 0 Oct 28 21:42 a (the execute permission also doesn't get set when I use the default umask 0022)