Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm 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 Message-ID: <40B78249.8050108@x-ray.at> Date: Fri, 28 May 2004 20:17:45 +0200 From: Reini Urban User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:1.7) Gecko/20040514 MultiZilla/1.5.0.4h MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: dll version collision References: <20040527212657.GC2617@ata.cs.hun.edu.tr> <7F99F48A-B0C5-11D8-BB92-000A95C4BF56@cipheroptics.com> <20040528171500.GC26698@coe.bosbc.com> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Michael Hale schrieb: > What is the correct way for someone to run multiple versions of cygwin > on their machine then? There's none! > This seems like a very useful feature to me, > since among other uses it would allow a new version to be tested along > side an older but known version of cygwin. Kill all cygwin processes (via net stop or psservice and then via taskman or pskill), backup the current cygwin1.dll and rename the new (snapshot) cygwin dll to cygwin1.dll, start the autostarting cygwin processes again (ipc-daemon2, cron, ...), test it. -- Reini Urban http://xarch.tu-graz.ac.at/home/rurban/ -- 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/