This is the mail archive of the
mailing list for the Cygwin project.
Re: setup.exe suggestion [firstname.lastname@example.org: Re: sshd dies]
- To: "Christopher Faylor" <cgf at redhat dot com>,<cygwin-apps at cygwin dot com>
- Subject: Re: setup.exe suggestion [email@example.com: Re: sshd dies]
- From: "Robert Collins" <robert dot collins at itdomain dot com dot au>
- Date: Sat, 10 Nov 2001 10:02:16 +1100
- References: <20011109111335.E24506@redhat.com>
----- Original Message -----
From: "Christopher Faylor" <firstname.lastname@example.org>
Sent: Saturday, November 10, 2001 3:13 AM
Subject: setup.exe suggestion [email@example.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
> 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.