Linux Container Development
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serge.hallyn-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>
To: Oren Laadan <orenl-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
Cc: Linux Containers
	<containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>,
	"Eric W. Biederman"
	<ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
Subject: Re: device(s) namespace
Date: Fri, 28 Jan 2011 08:33:04 -0600	[thread overview]
Message-ID: <20110128143304.GA4287@localhost> (raw)
In-Reply-To: <4D404C0E.6040603-eQaUEPhvms7ENvBUuze7eA@public.gmane.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

      parent reply	other threads:[~2011-01-28 14:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-26 16:30 device(s) namespace Oren Laadan
     [not found] ` <4D404C0E.6040603-eQaUEPhvms7ENvBUuze7eA@public.gmane.org>
2011-01-27 13:35   ` Serge E. Hallyn
2011-01-28 14:33   ` Serge E. Hallyn [this message]

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=20110128143304.GA4287@localhost \
    --to=serge.hallyn-z7wlfzj8ewms+fvcfc7uqw@public.gmane.org \
    --cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
    --cc=ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org \
    --cc=orenl-eQaUEPhvms7ENvBUuze7eA@public.gmane.org \
    /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