X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Message-ID: From: Jay To: , , , Subject: RE: setup v2.573.2.3: Postinstall: "abnormal exit: exit code=126" Date: Sun, 10 Aug 2008 12:59:42 +0000 In-Reply-To: <1218314204.10277.ezmlm@cygwin.com> References: <1218314204.10277.ezmlm@cygwin.com> Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id m7AD0a6Q027640 [again as plain text] ________________________________ > From: jayk123@hotmail.com > To: cygwin@cygwin.com; dave.korn@artimi.com; brian@dessent.net; andry@inbox.ru > Subject: Re: setup v2.573.2.3: Postinstall: "abnormal exit: exit code=126" > Date: Sun, 10 Aug 2008 08:35:51 +0000 > > [B] From: brian@ > > [B] ...I think...and we should just have > [B] bash provide /bin/sh directly without the complicated postinstall > [B] gymnastics. There was the objection that the current scheme obstensibly > [B] allows for the user to use any shell as /bin/sh, but I question how many > [B] people are aware of this let alone desire to take advantage of it. > > [D] From: dave.korn@ > ... > [D] The problem is that no matter whether bash or ash install /bin/sh, > [D] terminfo is going to be installed first, and that means > [D] /etc/postinstall/terminfo.sh is pretty much doomed to failure. [J] I assume Brian wants bash.tar.bz2 to just have a second copy of bash at bin/sh.exe, or a symlink or hardlink, unconditionally overwriting whatever is there. Rather than having a postinstall program copy it conditionally. ? And that all the extraction happens before any install code runs. ? - Jay -- 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/