Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Fri, 4 Apr 2003 10:26:06 -0500 From: "Pierre A. Humblet" To: cygwin AT cygwin DOT com Subject: Re: Postinstall failure: file not found Message-ID: <20030404152605.GA599585@Worldnet> References: <3E8DA250 DOT E8687FCA AT ieee DOT org> <20030404151741 DOT GA249497 AT Worldnet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030404151741.GA249497@Worldnet> User-Agent: Mutt/1.4i On Fri, Apr 04, 2003 at 10:17:41AM -0500, Pierre A. Humblet wrote: > > 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) ??? Don't use -c /> sh -c /sayhi /sayhi: not found /> sh /sayhi hi 7) ??? 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/