Re: cygwin1.dll, nontsec, and NTFS disk issue

2003-02-27 Thread Max Bowsher
Wu Yongwei wrote: You are correct about file permissions, Christopher. We all know that Windows has loose file permissions and all files are marked executable by default. When CYGWIN=nontsec, Old behaviour: when an executable is wanted, the system will check by extension and content, not

Re: cygwin1.dll, nontsec, and NTFS disk issue

2003-02-27 Thread Wu Yongwei
THANKS. Your message solved my problem. I used to set CYGWIN=nontsec in my .bashrc. Now I set it in cygwin.bat, and all works well. Best regards, Wu Yongwei --- Original Message from Max Bowsher --- New behaviour: when an executable is wanted, the system will check by file permissions on

Re: cygwin1.dll, nontsec, and NTFS disk issue

2003-02-27 Thread Christopher Faylor
On Thu, Feb 27, 2003 at 03:21:42PM +0800, Wu Yongwei wrote: You are correct about file permissions, Christopher. We all know that Windows has loose file permissions and all files are marked executable by default. When CYGWIN=nontsec, Old behaviour: when an executable is wanted, the system will

cygwin1.dll, nontsec, and NTFS disk issue

2003-02-26 Thread Wu Yongwei
With newer versions of cygwin1.dll (maybe 1.3.15 and later), the ntsec/nontsec behaviour has changed. Now ntsec is the default, and even when nontsec is specified, the command-line autocomplete still behaves like ntsec when operating on a NTFS disk, i.e., when I have a test.c and a test.exe,

Re: cygwin1.dll, nontsec, and NTFS disk issue

2003-02-26 Thread Thorsten Kampe
* Wu Yongwei (03-02-27 03:10 +0100) With newer versions of cygwin1.dll (maybe 1.3.15 and later), the ntsec/nontsec behaviour has changed. Now ntsec is the default, and even when nontsec is specified, the command-line autocomplete still behaves like ntsec when operating on a NTFS disk,

Re: cygwin1.dll, nontsec, and NTFS disk issue

2003-02-26 Thread Christopher Faylor
On Thu, Feb 27, 2003 at 04:13:00AM +0100, Thorsten Kampe wrote: * Wu Yongwei (03-02-27 03:10 +0100) With newer versions of cygwin1.dll (maybe 1.3.15 and later), the ntsec/nontsec behaviour has changed. Now ntsec is the default, and even when nontsec is specified, the command-line autocomplete

Re: cygwin1.dll, nontsec, and NTFS disk issue

2003-02-26 Thread Wu Yongwei
You are correct about file permissions, Christopher. We all know that Windows has loose file permissions and all files are marked executable by default. When CYGWIN=nontsec, Old behaviour: when an executable is wanted, the system will check by extension and content, not file permissions; New