[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070402142727.GF2456@in.ibm.com>
Date: Mon, 2 Apr 2007 19:57:27 +0530
From: Srivatsa Vaddagiri <vatsa@...ibm.com>
To: "Serge E. Hallyn" <serue@...ibm.com>
Cc: menage@...gle.com, akpm@...l.org, pj@....com, sekharan@...ibm.com,
dev@...ru, xemul@...ru, ebiederm@...ssion.com,
ckrm-tech@...ts.sourceforge.net, linux-kernel@...r.kernel.org,
containers@...ts.osdl.org, mbligh@...gle.com, winget@...gle.com,
rohitseth@...gle.com, devel@...nvz.org
Subject: Re: [ckrm-tech] [PATCH 7/7] containers (V7): Container interface to nsproxy subsystem
On Mon, Apr 02, 2007 at 09:09:39AM -0500, Serge E. Hallyn wrote:
> Losing the directory isn't a big deal though. And both unsharing a
> namespace (which causes a ns_container_clone) and mounting the hierarchy
> are done by userspace, so if for some installation it is a big deal,
> the init scripts on initrd can mount the hierarchy before doing any
> unsharing.
Yes I thought of that after posting this (that initrd can mount the
hierarchies), so this should not be an issue in practice ..
> Can you think of a reason why losing a few directories matters?
If we loose directories, then we don't have a way to manage the
task-group it represents thr' the filesystem interface, so I consider
that bad. As we agree, this will not be an issue if initrd
mounts the ns hierarchy atleast at bootup.
--
Regards,
vatsa
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists