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
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: Need name and functionality suggestions for a new utility
X-MimeOLE: Produced By Microsoft Exchange V6.0.4417.0
Date: Wed, 24 Oct 2001 15:29:25 +1000
Message-ID: <EA18B9FA0FE4194AA2B4CDB91F73C0EF08F21A@itdomain002.itdomain.net.au>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Need name and functionality suggestions for a new utility
Thread-Index: AcFcTEcpJx3J8MBjQ4GEhhmCF5SwWwAAAmHg
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: <cygwin-developers AT cygwin DOT com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id f9O5Nht05680



> -----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.

> I'd want to provide a mechanism for someone to isolate one cygwin
> release from another (which is probably something that I 
> vowed I'd never
> do, actually).  But, I don't want it to be too intrusive.
> 
> shm ids could be handled by changing the seeding of ftok(), though.

Errm, yes. So ftok() needs changing to accomodate this. 
 
> >>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.
 
> >I like isolate, it's pretty clear, and shouldn't create 
> mental conflict
> >with 'jail' or 'chroot'.  Also, howabout 'cygvirtual' or 
> 'cygalternate'
> >?
> >
> >Or even 'cygXP :}'.
> >
> >mycyg might be another one.
> 
> 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 ? 

Rob