Date: Mon, 9 Mar 2009 11:21:52 +0100
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Replacing setup.exe and cygcheck with dpkg (Was: Re: cygcheck 	typo in both manpage and --help)
Message-ID: <20090309102152.GS31459@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <5c01594c0903081410n548fdb1ewbb43692129942901@mail.gmail.com> <20090308211548.GA8625@ednor.casa.cgf.cx> <49B457E7.3010406@dazjorz.com> <20090309014539.GB8625@ednor.casa.cgf.cx> <20090309064422.GD6875@trikaliotis.net> <416096c60903090255m1e21f14dw94624232c94d6f61@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <416096c60903090255m1e21f14dw94624232c94d6f61@mail.gmail.com>
User-Agent: Mutt/1.5.19 (2009-02-20)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On Mar  9 09:55, Andy Koppe wrote:
> Spiro Trikaliotis:
> > You can replace a running exe (or dll) by doing the following:
> >
> > 1. rename the .DLL or .EXE
> 
> Are you sure that's possible? I'd expect Windows to complain loudly at
> that point.

You can in theory, but that won't work reliably for subsequent Cygwin
processes.  If you replace a running processes' executable with a new
release, and if that process is one of the forking kind, every
subsequent call to fork() will break.  If you replace the Cygwin DLL
with a new release on the fly, then *any* subsequent fork() will almost
surely break.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

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