Re: Executable flag

2005-11-04 Thread Arturus Magi
David Rasmussen wrote: 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. Part of the reason for this is because

Re: Executable flag

2005-10-26 Thread Igor Pechtchanski
On Wed, 26 Oct 2005, Brian Dessent wrote: > David Rasmussen wrote: > > > 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 w

Re: Executable flag

2005-10-26 Thread Brian Dessent
David Rasmussen wrote: > 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. This is really out of Cyg

Re: Executable flag

2005-10-26 Thread Joe Smith
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 The problem is that window

Re: Executable flag

2005-10-26 Thread David Rasmussen
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

Re: Executable flag

2005-10-26 Thread Eric Blake
> 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 n

Re: Executable flag

2005-10-26 Thread David Rasmussen
Thomas Cook wrote: try setting the umask to not include it. Okay. Is there a way to not have Windows applications (e.g. notepad) setting the x flag on every file created (as seen within cygwin)? /David -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports:

Executable flag

2005-10-26 Thread David Rasmussen
Is there anyway to have cygwin _not_ set the executable flag on every file it writes?? /David -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http