Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com Message-ID: <01b401c16972$94129ac0$0200a8c0@lifelesswks> From: "Robert Collins" To: "Christopher Faylor" , References: <20011109111335 DOT E24506 AT redhat DOT com> Subject: Re: setup.exe suggestion [ptsekov AT syntrex DOT com: Re: sshd dies] Date: Sat, 10 Nov 2001 10:02:16 +1100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-OriginalArrivalTime: 09 Nov 2001 23:08:23.0954 (UTC) FILETIME=[6E865F20:01C16973] ----- Original Message ----- From: "Christopher Faylor" To: Sent: Saturday, November 10, 2001 3:13 AM Subject: setup.exe suggestion [ptsekov AT syntrex DOT com: Re: sshd dies] > It probably would be a good idea to add an "is cygwin running?" check > to setup.exe. It could be a little tricky to determine, though, since > the name of the shared regions that cygwin uses can change. Errgh, I really don't like this. Checking if package foo is running before upgrading it, yes. Checking if cygwin is running at all, no. > I'm sort of loath to add a standard named entity in cygwin just to > accomodate setup.exe. > > Possibly, just walking through all of the processes and seeing if they've > loaded cygwin1.dll is a brute force approach. Which doesn't cover all cases :p. (Ie cygwin1.dll is only one file to be detected for write issues.) What we need is to be able to check for any of the .exe's or .dll's in a package, before uninstalling, and allow a [cancel][retry] option. You're right that the snapshot approach is probably best. Rob