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 01:34:45 -0400 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: Re: Need name and functionality suggestions for a new utility Message-ID: <20011024013445.C14370@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.21i On Wed, Oct 24, 2001 at 03:29:25PM +1000, Robert Collins wrote: > > >> -----Original Message----- >> From: Christopher Faylor [mailto:cgf AT redhat DOT com] >> >Also mmap id's, and any named objects that are file >> path/name based will >> >need alteration (prefix with 'MyOwnCygwin' ?). The cygwin daemon is >> >going to need adjustment for this as well. >> >> I don't think I want to go that crazy. This is just for >> cygwin objects. >> Theoretically, the whole mount table will look different so mmap >> objects, at least, will refer to different paths anyway. > >Ahh, touch /t >run prog that mmaps to /t >will conflict unless the named objects are created using win32 paths as >their basis. And for canonical behaviour using the unix path makes sense >to me. Well, mmap()ed (as in the system call mmap()) objects certainly are created using win32 paths. I'm modifying cygwin's "shared_name()" call to munge names in this environment, though. Hmm. How about cygnewenv? or just cygenv? Nah. Env has another meaning. >> >>cygjail maybe? cygisland? cygme? >> > >> >cygme with your coding trick? (aplogies to Ian Dury). >> >> Don't know the reference, sorry. > >"Hit me with your rhythm stick", - search for Ian Dury and the >Blockheads. I'm pretty sure you will recognise it if you hear it. Ok. Now I get it. >> Maybe. I don't like the prefix 'cyg' much but it does help reduce >> namespace pollution if we call all of the unique cygwin utilities >> cygsomething -- even if we strayed from that naming in the past. > >cygmycyg ? Cygidontthinksocyg cgf