9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Bakul Shah <bakul@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] A note about new software for Plan 9
Date: Mon, 11 Mar 2013 20:52:55 -0700	[thread overview]
Message-ID: <20130312035255.8C0CEB834@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Tue, 12 Mar 2013 03:17:37 -0000." <320203de502d79e73cd7447f3ce25154@sphericalharmony.com>

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.



  reply	other threads:[~2013-03-12  3:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-12  3:17 mycroftiv
2013-03-12  3:52 ` Bakul Shah [this message]
2013-03-12 14:57   ` Joel C. Salomon
2013-03-12 14:59     ` erik quanstrom
2013-03-12 18:27     ` Bakul Shah
  -- strict thread matches above, loose matches on Subject: below --
2013-03-13  2:51 mycroftiv
2013-03-12  4:20 mycroftiv
2013-03-12  5:56 ` Bakul Shah
2013-03-12 12:33   ` sl
2013-03-12  1:22 mycroftiv
2013-03-12  1:26 ` erik quanstrom

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130312035255.8C0CEB834@mail.bitblocks.com \
    --to=bakul@bitblocks.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).