From: "Eric Van Hensbergen" <ericvh@gmail.com>
To: weigelt@metux.de,
"Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] 1/2 OT: per-process mounts/namespace @ Linux
Date: Fri, 7 Sep 2007 15:15:48 -0500 [thread overview]
Message-ID: <a4e6962a0709071315j2e578c02m6be1f55d2b779e5c@mail.gmail.com> (raw)
In-Reply-To: <20070907200915.GA20929@nibiru.local>
Linux actually has private namespaces, its just off by default. There
is a flag to clone which can be used to establish new processes in
private namespaces (CLONENS or some such thng).
Primary downside is that its superuser only -- but you could get
around it with setuid or custom kernel.
-eric
On 9/7/07, Enrico Weigelt <weigelt@metux.de> wrote:
>
> Hi folks,
>
>
> I was just reading some older mails on this list and thinking
> about how to mimic the plan9 behaviour of local namespaces on
> Linux. My idea is:
>
> * each namespace is just some directory, ie. living somewhere
> under /.NAMESPACES/, maybe /.NAMESPACES/<pid>/
> * these namespaces are maintained by either some daemon or
> an special synthetic filesystem
> * processes with private namespaces are chroot()'ed to their
> own namespace directory.
>
>
> What do you think about this ?
>
>
> cu
> --
> ---------------------------------------------------------------------
> Enrico Weigelt == metux IT service - http://www.metux.de/
> ---------------------------------------------------------------------
> Please visit the OpenSource QM Taskforce:
> http://wiki.metux.de/public/OpenSource_QM_Taskforce
> Patches / Fixes for a lot dozens of packages in dozens of versions:
> http://patches.metux.de/
> ---------------------------------------------------------------------
>
next prev parent reply other threads:[~2007-09-07 20:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-07 20:09 Enrico Weigelt
2007-09-07 20:15 ` Eric Van Hensbergen [this message]
2007-09-07 21:26 ` David Leimbach
2007-09-07 21:38 ` Charles Forsyth
2007-09-07 22:21 ` Latchesar Ionkov
2007-09-07 22:27 ` Eric Van Hensbergen
2007-09-07 22:45 ` ron minnich
2007-09-07 22:45 ` ron minnich
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=a4e6962a0709071315j2e578c02m6be1f55d2b779e5c@mail.gmail.com \
--to=ericvh@gmail.com \
--cc=9fans@cse.psu.edu \
--cc=weigelt@metux.de \
/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).