From mboxrd@z Thu Jan  1 00:00:00 1970
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
In-reply-to: Your message of "Tue, 12 Mar 2013 03:17:37 -0000."
	<320203de502d79e73cd7447f3ce25154@sphericalharmony.com>
References: <320203de502d79e73cd7447f3ce25154@sphericalharmony.com>
Date: Mon, 11 Mar 2013 20:52:55 -0700
From: Bakul Shah <bakul@bitblocks.com>
Message-Id: <20130312035255.8C0CEB834@mail.bitblocks.com>
Subject: Re: [9fans] A note about new software for Plan 9
Topicbox-Message-UUID: 2793d4c6-ead8-11e9-9d60-3106f5b1d025

Just a suggestion:

Some motivating examples may help.  Perhaps you can show
1. Initial state of the world (show with the help of a few ls)
2. A sequence of commands to change it
3. What the world looks like finally

And a brief description why this would be desirable.  And how
it compares with just using chroot. Most people here can
perhaps read rc code more readily than elaborate explanations!

In *BSD a jail is more than chroot since it can also get access
to its own interfaces, networking stack, init process, devices
etc. And it can't look at the state of another jail or the
host. And another host on the net doesn't even know it is
talking to a jail.

To do something similar you will have to constrain each jail
to see a subset of processes, give it its own /dev, /env etc.
Not sure how you do this.