X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Sat, 9 Jan 2010 23:28:27 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Update problems Message-ID: <20100110042827.GA21035@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <4B46A4C3 DOT 2000803 AT cygwin DOT com> <4B47986F DOT 2020609 AT t-online DOT de> <4B47B3FA DOT 1010101 AT cygwin DOT com> <4B47DBAE DOT 5000901 AT monai DOT ca> <20100109100941 DOT GL23992 AT calimero DOT vinschen DOT de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100109100941.GL23992@calimero.vinschen.de> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , 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 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. However, people will keep suggesting that it is possible to do this without offering concrete suggestions for at least the next ten years. 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