Date: Fri, 13 Nov 2009 12:01:22 -0500
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Suggestion: Have setup.exe warn before upgrading 'cgywin'  package  itself
Message-ID: <20091113170122.GC22412@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <26327934 DOT post AT talk DOT nabble DOT com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <26327934.post@talk.nabble.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

On Thu, Nov 12, 2009 at 02:46:12PM -0800, aputerguy wrote:
>
>Currently when upgrading the base 'cygwin' package, the installer only warns
>you midway through the installation after some files have been
>removed/replaced.
>
>If you have other cygwin processes running, you may be left in an incomplete
>state where you can't or don't want to kill the other cygwin processes
>leaving you stuck in the middle of install while you wait to be able to
>finish or kill the existing cygwin processes. Even worse, several core
>cygwin utilities are now broken (such as 'ps') due to the partial install.
>
>I have done this inadvertently a couple of times when 'cygwin' gets thrown
>in as a part of another intentioned download.
>
>Today I was left in an even odder state since I ran 'setup.exe' from a bash
>prompt -- leaving me in a catch-22 since if I kill the bash processes then I
>kill setup but I can't continue until I kill the bash processes...

Why would doing a "kill -9" on the bash process kill setup.exe?  There is no
reason for that to happen.

cgf

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