Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Date: Wed, 24 Oct 2001 01:29:42 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-developers AT cygwin DOT com
Subject: Re: Need name and functionality suggestions for a new utility
Message-ID: <20011024012942.B14370@redhat.com>
Reply-To: cygwin-developers AT cygwin DOT com
Mail-Followup-To: cygwin-developers AT cygwin DOT com
References: <20011024005137 DOT A29851 AT redhat DOT com> <3BD64F1E DOT 6010102 AT ece DOT gatech DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3BD64F1E.6010102@ece.gatech.edu>
User-Agent: Mutt/1.3.21i

On Wed, Oct 24, 2001 at 01:18:22AM -0400, Charles Wilson wrote:
>Christopher Faylor wrote:
>
>Neat idea.
>
>
>>Does anyone have an idea for a name?  Or even an idea for more
>>functionality for this utility?  Now that I think of it, this utility
>>should also change the shared memory id 
>
>Can you DO that without adding hooks to cygwin1.dll?

No.  You need to add some hooks.  The cygheap changes that I made a while
ago make this very easy, though.

I had the hooks written and cygwin compiled.  Then, sending this email
started a whole flood of new ideas about what needed to be changed.

I think it might just be possible to allow two different cygwins to
coexist without this as long as they share the mount table.  I don't
know if that's a good thing or not.

It means that instead of getting "shared memory mismatch" we'll be hearing
about how the new version of cygwin doesn't fix their problems -- because
they still have a cygwin1.dll in their windows/system directory.

Hmm.  Maybe I should make cygwin1.dll complain if it is placed in the
windows/system directory.

Why do I suddenly picture Bugs Bunny saying "Ain't I a stinker"...?

cgf