Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Date: Tue, 8 May 2001 00:13:15 -0400 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: _cygwin_S_IEXEC we hardly knew ye Message-ID: <20010508001315.A4844@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i I've gotten rid of the crap in /usr/include/sys/{stat,unistd,file}.h for dealing with S_IEXEC. It was obviously going to cause more problems than it was worth. The variables are still around to accomodate programs that may have used the header files and libcygwin.a but they don't do anything special anymore. Their use in 1.3.1 was supposed to trigger the checking of magic numbers and #! in files so that cygwin could set the execute bit. Now, I've reverted to always checking the execute bit, just like before. For 1.3.3, I am going to implement a "Don't check this directory for execute bits" option to mount. I'd like to have this on by default for smb drives. Does this sound like a good idea? cgf