> 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. For any more help from us, you need to give a better problem report, preferably including instructions of how to reproduce a scenario where you think cygwin was doing the wrong thing. > Problem reports: http://cygwin.com/problems.html -- Eric Blake -- 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/
