public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tim Hockin <thockin@hockin.org>
To: Rik van Riel <riel@redhat.com>
Cc: Hans Reiser <reiser@namesys.com>,
	LKML <linux-kernel@vger.kernel.org>,
	ReiserFS List <reiserfs-list@namesys.com>,
	michael.waychison@sun.com
Subject: Re: Using fs views to isolate untrusted processes: I need an assistant architect in the USA for Phase I of a DARPA funded linux kernel project
Date: Wed, 25 Aug 2004 13:56:18 -0700	[thread overview]
Message-ID: <20040825205618.GA7992@hockin.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0408251624540.5145-100000@chimarrao.boston.redhat.com>

On Wed, Aug 25, 2004 at 04:25:24PM -0400, Rik van Riel wrote:
> > You can think of this as chroot on steroids.
> 
> Sounds like what you want is pretty much the namespace stuff
> that has been in the kernel since the early 2.4 days.
> 
> No need to replicate VFS functionality inside the filesystem.

When I was at Sun, we talked a lot about this.  Mike, does Sun have any
iterest in this?

We found a lot of shortcomings in implementing various namespace-ish
things.


  reply	other threads:[~2004-08-25 21:15 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-02  1:20 Using fs views to isolate untrusted processes: I need an assistant architect in the USA for Phase I of a DARPA funded linux kernel project Hans Reiser
2004-08-25 20:25 ` Rik van Riel
2004-08-25 20:56   ` Tim Hockin [this message]
2004-08-25 21:23     ` Mike Waychison
2004-08-26  6:31       ` Hans Reiser
2004-08-26 13:59         ` Stephen Smalley
2004-08-25 23:19     ` Kyle Moffett
2004-08-26  0:16       ` Mike Waychison
2004-08-26  0:50         ` Kyle Moffett
2004-08-26  1:06           ` Chris Wright
2004-08-26  4:16             ` Kyle Moffett
2004-08-26  4:29               ` viro
2004-08-26  4:52                 ` Kyle Moffett
2004-08-26  5:01                   ` viro
2004-08-26  0:56         ` Chris Wright
2004-08-26  7:52         ` Hans Reiser
2004-08-26  8:48   ` Hans Reiser

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=20040825205618.GA7992@hockin.org \
    --to=thockin@hockin.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael.waychison@sun.com \
    --cc=reiser@namesys.com \
    --cc=reiserfs-list@namesys.com \
    --cc=riel@redhat.com \
    /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