X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Sun, 10 Jan 2010 12:00:29 +0100 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: Update problems Message-ID: <20100110110029.GC9041@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <4B46A4C3.2000803@cygwin.com> <4B47986F.2020609@t-online.de> <4B47B3FA.1010101@cygwin.com> <4B47DBAE.5000901@monai.ca> <20100109100941.GL23992@calimero.vinschen.de> <20100110042827.GA21035@ednor.casa.cgf.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100110042827.GA21035@ednor.casa.cgf.cx> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Jan 9 23:28, Christopher Faylor wrote: > On Sat, Jan 09, 2010 at 11:09:41AM +0100, Corinna Vinschen wrote: > >The most pressing problem is the replacement of the cygwin DLL itself. > >It's like installing a new kernel in Linux. However, in Linux you have > >to reboot to use the new kernel, while Cygwin is just a DLL. After the > >rename and replace operation, existing processes will use the old DLL > >while new processes will use the new DLL. This is bound to break and > >there's no clean way to do it, except to replace the Cygwin DLL while > >no other Cygwin process is running. > > In other words, the problem which has always been the problem is still > the problem. A fair summary. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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