X-Spam-Check-By: sourceware.org Message-ID: <4609A2F9.DEE6E246@dessent.net> Date: Tue, 27 Mar 2007 16:04:25 -0700 From: Brian Dessent X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Files getting 'x' permission installing packages in Cygwin References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Angelo Graziosi wrote: > Is it 'normal' that, when one installs packages, files, like *.a, *.h, > *.README etc. (i.e. files that normally are not executables), acquires the > 'x' permission ? Yes. Just as normal as if you created the file in a regular Windows application; it will get the default ACL as defined by the standard NTFS inheritance rules (parent directory, etc.) > In the tar ball of the corresponding packages they do not have 'x'! > > Could this have to do with 'setup.exe' (I am using 2.558 snapshot) ? Setup is not a Cygwin program, it is a native Windows program. It does not contain any of the "ntsec" logic needed to map POSIX modes onto Windows ACLs. It would be a lot of duplication to reimplement all of this outside of Cygwin, and apparently it is not necessary. This is also why postinstall and preremove scripts run with the CYGWIN=nontsec environment set, so that files created there have matching semantics. Brian -- 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/