Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Thu, 27 Feb 2003 09:43:57 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: cygwin1.dll, nontsec, and NTFS disk issue Message-ID: <20030227144357.GA5638@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <3E5DBC86 DOT 1030509 AT netstd DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3E5DBC86.1030509@netstd.com> User-Agent: Mutt/1.5.1i 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 check by >extension and content, not file permissions; > >New behaviour: when an executable is wanted, the system will check by >file permissions on NTFS disks, even though nontsec is set. And, don't you think I checked this before responding? On MY system, setting CYGWIN=nontsec causes the executable bits to disappear. My next theory is that you may be setting CYGWIN=nontsec directly in bash or something. You have to set CYGWIN=nontsec prior to starting a cygwin process. Please provide the exact details of what you are doing, along with cygcheck -r -s -v output as an attachment. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/