X-Spam-Check-By: sourceware.org
Date: Tue, 26 Dec 2006 01:47:05 -0500
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Updated cygwin dlls cause unnecessary reboot on NT
Message-ID: <20061226064704.GA6923@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <458EE598 DOT 3010404 AT aim DOT com> <458F31B1 DOT 6050804 AT byu DOT net> <458F81CC DOT 3090500 AT tlinx DOT org> <458FDC4E DOT 9040505 AT cygwin DOT com> <458FEC2E DOT 70705 AT tlinx DOT org> <Pine DOT GSO DOT 4 DOT 63 DOT 0612251346240 DOT 27982 AT access1 DOT cims DOT nyu DOT edu> <45902BC4 DOT 50803 AT tlinx DOT org> <4590BD4E DOT 5020905 AT cygwin DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4590BD4E.5020905@cygwin.com>
User-Agent: Mutt/1.5.11
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

On Tue, Dec 26, 2006 at 01:12:30AM -0500, Larry Hall (Cygwin) wrote:
>On 12/25/2006, Linda Walsh wrote:
>>FWIW, I have replaced the libs like cygwin1.dll, cygintl?.dll...  and
>>such while cygwin is running and not had a catastrophe as one might
>>have trying to overwrite/update the memory image of a kernel
>>dynamically, so I don't think it's quite all the end of the world you
>>make it out to be.  But I admit it doesn't sound clean.
>
>It's more than that regardless of your (lucky) experiences.  It is that
>way for a reason, whether or not you know or understand it.  However,
>if your short-cut works well for you in your usage, more power to you.
>It can't be advocated as a general solution for cygwin1.dll though.
>
>It's also worthwhile to note that the Cygwin web site still states that
>"The Cygwin DLL works with all non-beta, non "release candidate", ix86
>32 bit versions of Windows since Windows 95, with the exception of
>Windows CE." So regardless of how XP and later platforms may handle DLL
>replacements, 'setup.exe' still needs to handle the cases prior to the
>more advanced techniques you mention.  For now, that means 'setup.exe'
>works as it always has, until someone offers a patch to make it more
>discriminating.  That someone could be you! ;-)

Such an optimist...

cgf

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