Quoting Herbert Poetzl (herbert@13thfloor.at):
> On Wed, Dec 13, 2006 at 10:36:33AM -0800, Dave Hansen wrote:
> > On Wed, 2006-12-13 at 08:35 -0600, Serge E. Hallyn wrote:
> > >
> > >         struct container {
> > >                 struct container *parent;
> > >                 char *name;
> > >                 struct nsproxy *nsproxy;
> > >                 struct list_head children;
> > >         };
> > >         struct nsproxy {
> > >                 ...
> > >                 struct container *container;
> > >         };
> >
> > Why does a container need a pointer to an nsproxy?  I think I missed
> > that.  Is that the "default" set of namespaces for tasks in that
> > container?
> 
> IMHO it is mainly required to _enter_ the container
> in some controlled way (at least that is what we
> use the nsproxy reference for)

Exactly, it is there to facilitate entering containers.

-serge
_______________________________________________
Containers mailing list
Containers@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/containers