Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
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
From: ericblake AT comcast DOT net (Eric Blake)
To: "Williams, Gerald S (Jerry)" <gsw AT agere DOT com>, cygwin AT cygwin DOT com
Subject: RE: SETUP: In-use files have been replaced
Date: Tue, 18 Oct 2005 19:51:51 +0000
Message-Id: <101820051951.5392.43555257000330970000151022064246130A050E040D0C079D0A@comcast.net>

> > Your situation isn't normal because you didn't stop all cygwin
> > services.  While the idea has been tossed around on this list
> > that it would be nice if setup.exe could stop services for you,
> > to date, it does not.  Therefore, IT IS UP TO YOU to stop services
> > beforehand.
> 
> Thanks. I remember one of the Cygwin major contributors
> indicating that (s)he didn't find the need to stop the
> Cygwin services first, but perhaps I misunderstood.

I believe you are referring to the recent question about whether
cygwin services must be stopped during a WINDOWS upgrade,
which is a different matter entirely from cygwin upgrades.  The
answer there was that it is usually safe to leave cygwin running
during a windows upgrade, although the recent directx 9 patch
on Win2k proved to be a counterexample.

But when it comes to running cygwin while upgrading cygwin,
the consensus on this list is that it is safest and simplest to
just always stop all cygwin processes before starting setup.exe.

--
Eric Blake



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