X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Message-ID: <489DF631.57D5D4D6@dessent.net> Date: Sat, 09 Aug 2008 12:55:29 -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: setup v2.573.2.3: Postinstall: "abnormal exit: exit code=126" References: <1078355474 DOT 20080809162543 AT inbox DOT ru> <00be01c8fa36$aaa16120$9601a8c0 AT CAM DOT ARTIMI DOT COM> 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 Dave Korn wrote: > I'll try and think up a fix for this. In the meantime, you can work I'll repeat my previous opinion on this issue: I think the time for compensating for the ash -> bash upgrade is over and we should just have bash provide /bin/sh directly without the complicated postinstall gymnastics. There was the objection that the current scheme obstensibly allows for the user to use any shell as /bin/sh, but I question how many people are aware of this let alone desire to take advantage of it. 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/