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 Message-ID: <001b01c2de51$60658b60$78d96f83@pomello> From: "Max Bowsher" To: "Wu Yongwei" , "cygwin" References: <3E5DBC86 DOT 1030509 AT netstd DOT com> Subject: Re: cygwin1.dll, nontsec, and NTFS disk issue Date: Thu, 27 Feb 2003 11:14:20 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 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. ^^^^^^^^^^^^^^^^^^^^^^^^^^ You *are* setting nontsec *before* starting bash, right? Max. -- 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/