X-Recipient: archive-cygwin@delorie.com
X-Spam-Check-By: sourceware.org
Date: Mon, 22 Jun 2009 11:43:10 +0200
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Cygwin 1.7: Possible file permission errors in 'base-files'
Message-ID: <20090622094310.GN5039@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <4A3D1570.5020506@aim.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4A3D1570.5020506@aim.com>
User-Agent: Mutt/1.5.19 (2009-02-20)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

On Jun 20 12:59, Mark Harig wrote:
>
> The two files 'base-files-mketc.sh' and 'base-files-profiles.sh' included
> in the 'base-files' package have their permissions set to 644 while all
> other scripts in /etc/postinstall/ have their permissions set to 755.
>
> Is this a side-effect of 'base-files-profiles.sh' not completing without
> errors, or is this set in the packaging?
>
> (Technically, the files with the permission problems are
> /etc/postinstall/base-files-mketc.sh.done and
> /etc/postinstall/base-files-profiles.sh.done.)

Technically it's a packaging bug.  The scripts should have execute
permissions like all the shell scripts in /etc/postinstall and
/etc/preremove.

John, I fixed that on Sourceware and created a 3.8-4 package with
execute permissions for postinstall and preremove scripts.

It shouldn't affect postinstall, though.  When calling `bash -c script',
then bash runs these scripts as long as the user has read permissions
on Cygwin.  Which is actually kind of a bug in Cygwin.  I've put that
on my TODO list.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

