Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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 11:43:53 +0400 From: egor duda X-Mailer: The Bat! (v1.53 RC/4) Reply-To: egor duda Organization: deo X-Priority: 3 (Normal) Message-ID: <195555408.20011024114353@logos-m.ru> To: Christopher Faylor Subject: Re: Need name and functionality suggestions for a new utility In-Reply-To: <20011024012942.B14370@redhat.com> References: <20011024005137 DOT A29851 AT redhat DOT com> <3BD64F1E DOT 6010102 AT ece DOT gatech DOT edu> <20011024012942 DOT B14370 AT redhat DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi! Wednesday, 24 October, 2001 Christopher Faylor cgf AT redhat DOT com wrote: CF> On Wed, Oct 24, 2001 at 01:18:22AM -0400, Charles Wilson wrote: >>Christopher Faylor wrote: >>>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? CF> No. You need to add some hooks. The cygheap changes that I made a while CF> ago make this very easy, though. does your tweak works in such scenario? "cygwin-app-1" starts "non-cygwin-app-2" and it starts "cygwin-app-3" will cygwin-app-3 be properly "jailed"? i was supposing to write a patch to add (ahem) yet another CYGWIN env variable option so one can write, e.g. 'set CYGWIN=profile:old_install' CF> I had the hooks written and cygwin compiled. Then, sending this email CF> started a whole flood of new ideas about what needed to be changed. CF> I think it might just be possible to allow two different cygwins to CF> coexist without this as long as they share the mount table. I don't CF> know if that's a good thing or not. CF> It means that instead of getting "shared memory mismatch" we'll be hearing CF> about how the new version of cygwin doesn't fix their problems -- because CF> they still have a cygwin1.dll in their windows/system directory. this can be easily revealed by cygcheck. CF> Hmm. Maybe I should make cygwin1.dll complain if it is placed in the CF> windows/system directory. and this too. Egor. mailto:deo AT logos-m DOT ru ICQ 5165414 FidoNet 2:5020/496.19