Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Message-Id: <4.3.1.2.20020315150903.0169bc60@pop.ma.ultranet.com> X-Sender: lhall@pop.ma.ultranet.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Fri, 15 Mar 2002 15:09:50 -0500 To: cygwin@cygwin.com From: "Larry Hall (RFK Partners, Inc)" Subject: Re: cygwin.com suggestions In-Reply-To: <3C92525C.6070403@Salira.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 02:58 PM 3/15/2002, Andrew DeFaria wrote: >Robert Collins wrote: > >>>2) Include in the FAQ (or somewhere) a section on "How to Safely Update the Cygwin dll". Probably just "shut down all cygwin apps, including daemons", but it would be useful to know for sure. >>The next release of setup.exe automatically address's this and will >>replace in-use .dll's. > >Really? How does it do that? Because I was under the impression that if a program was running you cannot replace it's .exe file (or .dll file) because it was opened exclusively by Windows. How do you get around that? Same way as Windows installers work. Just schedule the DLL to be moved in after reboot. Larry Hall lhall@rfk.com RFK Partners, Inc. http://www.rfk.com 838 Washington Street (508) 893-9779 - RFK Office Holliston, MA 01746 (508) 893-9889 - FAX -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/