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:17:40 +1000
Message-ID: <EA18B9FA0FE4194AA2B4CDB91F73C0EF7A40@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: AcFcSI3hMrMb2nuMSy6nLYgIkK4uFAAAXe0Q
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 f9O59hG04275



> -----Original Message-----
> From: Christopher Faylor [mailto:cgf AT redhat DOT com]

> So, we eventually came up with the idea of something like a 'chroot'
> utility where you could say something like:
> 
> cygisolate MyOwnCywin bash
> 
> and that bash and all of its children would use MyOwnCygwin as the
> registry key rather than "Cygwin".
> 
> This would mean that you could have an isolated set of mounts which
> would not be touched by something not in the cygisolate "tree".
> 
> The concept is similar to chroot.  It is so similar that I'm tempted
> to just add a switch to chroot to handle this but I hate hacking up
> existing utilities for Cygwin's purposes.

Well, chroot doesn't address shmid's and the like, and this will need
to. 

> So, I've got everything written to accomodate this usage but I'm stuck
> on a name.  I don't like cygisolate but I can't think of 
> anything else.
> 
> 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 so that there are no conflicts
> between this cygwin and another running instance.

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.
 
> cygjail maybe?
> cygisland?
> cygme?

cygme with your coding trick? (aplogies to Ian Dury).

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.

Rob