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 Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <013101c1a4bf$9c3b10f0$0200a8c0@lifelesswks> From: "Robert Collins" To: "Wu Yongwei" , References: <000701c1a4bf$59db2f10$0610a8c0 AT wyw> Subject: Re: File mode judgement Date: Thu, 24 Jan 2002 21:12:19 +1100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-OriginalArrivalTime: 24 Jan 2002 10:12:20.0779 (UTC) FILETIME=[9C1AB7B0:01C1A4BF] === ----- Original Message ----- From: "Wu Yongwei" To: Sent: Thursday, January 24, 2002 9:10 PM Subject: File mode judgement > In the past, Cygwin seemed to judge whether a file is executable on a > combination of suffix and content. However, today when I reinstalled Cygwin, > I suddenly found that it no more did it. Now on a NTFS volume it depends > only on file attributes. > > 1) Is it a design change? Yes. It is much faster to look at file permissions first, and content second. Thats what unix does. The change is activated by CYGWIN=ntsec. > 2) Is it possible to switch back to the old behaviour? AFAIK, no. It shouldn't be needed anyway, just use chmod to set the +x bit on any executables you have. Rob -- 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/