Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Sun, 16 Jan 2005 20:13:43 -0500
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Can "DLL's" & libraries be marked as non-executable?
Message-ID: <20050117011343.GE12175@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
References: <41E9D722 DOT 3010306 AT tlinx DOT org> <009001c4fba2$54223c20$e6ec6f83 AT robinson DOT cam DOT ac DOT uk> <41EAF139 DOT 6070102 AT tlinx DOT org> <41EAFB0B DOT 8080501 AT familiehaase DOT de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <41EAFB0B.8080501@familiehaase.de>
User-Agent: Mutt/1.4.1i

On Mon, Jan 17, 2005 at 12:38:51AM +0100, Gerrit P. Haase wrote:
>>More to the point, what would "break" in the cygwin environment,
>
>Try to chmod 644 any dll and call a program that uses this dll.  This
>fails for me (on NT4 with NTFS), if it succeeds for you, fine.  Change
>the permissions as you like it;)

I think what's being asked is that we make a special case for dlls so
that, even if the OS says they are executable, cygwin will not call them
executable.

--
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/