X-Recipient: archive-cygwin@delorie.com
X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 	tests=AWL,BAYES_00,SPF_SOFTFAIL
X-Spam-Check-By: sourceware.org
Message-ID: <4B4A3918.4020005@byu.net>
Date: Sun, 10 Jan 2010 13:31:20 -0700
From: Eric Blake <ebb9@byu.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; 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@cygwin.com
Subject: Re: Update problems
References: <web-28750510@remus.csulb.edu>  <4B46A4C3.2000803@cygwin.com>  <4B47986F.2020609@t-online.de>  <4B47B3FA.1010101@cygwin.com>  <4B47DBAE.5000901@monai.ca>  <20100109100941.GL23992@calimero.vinschen.de>  <4B4A1032.9030201@monai.ca> <20100110192728.GC24855@ednor.casa.cgf.cx>
In-Reply-To: <20100110192728.GC24855@ednor.casa.cgf.cx>
Content-Type: multipart/signed; micalg=pgp-sha1;  protocol="application/pgp-signature";  boundary="------------enig58895B66B3B07D7B3CFA2EFB"
X-IsSubscribed: yes
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

--------------enig58895B66B3B07D7B3CFA2EFB
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

According to Christopher Faylor on 1/10/2010 12:27 PM:
> This idea has been put forth many times since that time.  The fact that
> it isn't implemented means that either 1) It's more difficult than you
> anticipate or 2) No one thinks its a good idea.

And here's one reason why.  Newer versions of cygwin1.dll introduce new
entry points.  But suppose you are updating cygwin1.dll and bash at the
same time.  If the new bash depends on one of those new entry points, but
the old cygwin1.dll is still in operation, then the replace-on-reboot
won't save the fact that the new bash won't work until the reboot.

Really, it is better to stop ALL things cygwin, do the upgrade, and not
worry about those interactions.

--=20
Don't work too hard, make some time for fun as well!

Eric Blake             ebb9@byu.net


--------------enig58895B66B3B07D7B3CFA2EFB
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAktKOR0ACgkQ84KuGfSFAYCoogCfSRgXBzrUkqXw2L7uW9BOLaSa
2joAn0hLwsqX72gHr2PKBsxxEeY+ndZr
=NBrM
-----END PGP SIGNATURE-----

--------------enig58895B66B3B07D7B3CFA2EFB--
