Need name and functionality suggestions for a new utility

Robert Collins robert.collins@itdomain.com.au
Tue Oct 23 22:09:00 GMT 2001


> -----Original Message-----
> From: Christopher Faylor [ mailto:cgf@redhat.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



More information about the Cygwin-developers mailing list