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 <[EMAIL PROTECTED]> 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/
> ---------------------------------------------------------------------
>
