X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-3.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By:	sourceware.org
Message-ID:	<4B21E157.20701@cwilson.fastmail.fm>
Date:	Fri, 11 Dec 2009 01:06:15 -0500
From:	Charles Wilson <cygwin AT cwilson DOT fastmail DOT fm>
User-Agent:	Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: Is 1.7 ready?/Installation Issues
References:	<873a3i5phc DOT fsf AT jondo DOT cante DOT net> <4B21DA6F DOT 7020706 AT kringlecottage DOT com>
In-Reply-To:	<4B21DA6F.7020706@kringlecottage.com>
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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 & Diane wrote:

> I appreciate that I'm not giving you a lot to go on here, but my gut
> tells me there are some serious gremlins in the guts and in the
> installation still, it certainly prevents me from moving my 1.5 system
> to 1.7 at work and I'm worried that if 1.7 is released you'll be
> overwhelmed with support requests that are eerily similar. This is why I
> ask if 1.7 is ready for prime time. Perhaps I'm just being unlucky, and
> thats ok.

I'm assuming you've checked for BLODAs, and that you have no known or
suspected BLODAs running.  In that case...

My gut says that the postinstall scripts are encountering the dreaded
"*** unable to remap" error, which (a) takes a few seconds before cygwin
gives up and reports it (to setup; you won't see the error message), and
(b) leaves a zombie process running around. If this occurs every time
setup tries to run a postinstall script, and there are 40-50 such
scripts in a typical 'virgin' installation, then...pain.

My suggestion is: if everything has actually been downloaded and
installed, and only the postinstall scripts are causing problems, then
kill setup, and manually:

launch cmd
cd C:\cygwin-1.7\bin
ash
rebaseall -v
for f in /etc/postinstall/*.sh ; do
  /bin/bash -c $f && mv $f $f.done
done

But...take all that with a grain of salt.  It's just my gut feeling with
very little evidence to back it up.

--
Chuck

--
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

- Raw text -