Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Fri, 4 Apr 2003 10:17:41 -0500 From: "Pierre A. Humblet" To: cygwin@cygwin.com Subject: Re: Postinstall failure: file not found Message-ID: <20030404151741.GA249497@Worldnet> References: <3E8DA250.E8687FCA@ieee.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3E8DA250.E8687FCA@ieee.org> User-Agent: Mutt/1.4i On Fri, Apr 04, 2003 at 10:18:40AM -0500, Pierre A. Humblet wrote: > OK, I've got it: > > /> sh -c sayhi > hi > /> sh -c /sayhi > /sayhi: not found > > With strace I saw that sh uses stat (which won't show rxw rights > in this case) and it behaves differently for absolute paths. > > Possible fixes: > 1) cd to /etc/postinstall before running the scripts and use relative paths > 2) Put my 2nd ntsec patch in setup (I have asked Rudiyanto to test it) > 3) Run the postinstall scripts with CYGWIN=nontsec, for boostrap. > Note that scripts that rely on ntsec (chmod or chown) will need to turn > ntsec on. > 4) patch sh.exe > 5) ??? Use bash /> bash -c /sayhi hi /> bash -c sayhi hi 6) ??? Pierre -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/