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: <435FEED2.3040309@gmx.net> Date: Wed, 26 Oct 2005 23:02:10 +0200 From: David Rasmussen User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Executable flag References: <102620052059 DOT 5236 DOT 435FEE1400022CF60000147422007348300A050E040D0C079D0A AT comcast DOT net> In-Reply-To: <102620052059.5236.435FEE1400022CF60000147422007348300A050E040D0C079D0A@comcast.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Eric Blake wrote: >>Is there anyway to have cygwin _not_ set the executable flag on every >>file it writes?? > > On NTFS, where POSIX semantics can be emulated, cygwin obeys > POSIX default rules (creating or opening a file does not set the > x bits unless specially requested). On FAT, where the file system > has no good support, cygwin is helpless. So I fail to reproduce > the problem you are reporting. You may also want to consider > using umask. > Okay, a reproducable example: Open cygwin. Write 'notepad test.txt'. Notepad opens, write something and then save the file. Now do an ll. The file test.txt has been created and has the executable flag set. I want it to not be set in such cases. /David -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/