From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Serge E. Hallyn" Subject: Re: device(s) namespace Date: Fri, 28 Jan 2011 08:33:04 -0600 Message-ID: <20110128143304.GA4287@localhost> References: <4D404C0E.6040603@cs.columbia.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <4D404C0E.6040603-eQaUEPhvms7ENvBUuze7eA@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: Oren Laadan Cc: Linux Containers , "Eric W. Biederman" List-Id: containers.vger.kernel.org Quoting Oren Laadan (orenl-eQaUEPhvms7ENvBUuze7eA@public.gmane.org): > Hi, > > I vaguely recall some discussions/ideas about the possibility > of a devices namespace, its pros and cons, and alternative. > Related to that is also device viruatlization, and isolation > of devices in containers. > > Any thoughts and or pointers to past/current discussions are > welcome :) > > Thanks, What I find in my old containers folders when grepping for 'device namespace' is mainly vague references to devicens as a more ideal solution to other patches being submitted (namely the device cgroup, the sysfs directory tagging, and ptyns). A link which was referenced in one of those emails: https://lists.linux-foundation.org/pipermail/containers/2008-April/010810.html So while I'm pretty sure I have in the past seen discussions on what the device namespace would look like, they must have been on irc or in person. -serge