From mboxrd@z Thu Jan 1 00:00:00 1970 From: Janne Karhunen Subject: Re: RFC: Device Namespaces Date: Wed, 25 Sep 2013 14:05:32 +0300 Message-ID: References: <20130822182118.GA28331@sergelap> <8761udlu0d.fsf@xmission.com> <871u4yddg4.fsf@xmission.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: 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: Amir Goldstein Cc: Linux Containers , "Eric W. Biederman" , lxc-devel List-Id: containers.vger.kernel.org On Tue, Sep 10, 2013 at 10:09 AM, Amir Goldstein wrote: > On Mon, Sep 9, 2013 at 2:51 AM, Eric W. Biederman wrote: > >> Amir Goldstein writes: >> >> > On Fri, Sep 6, 2013 at 7:50 PM, Eric W. Biederman >> > wrote: >> > >> > Hi Eric, >> > >> > If we can get people to take a quick look at the code before LPC >> > that could make the LPC discussions more effective. Hi, I think we are curious enough to experiment with Erics idea of implementing basic 'device namespace' in userspace (never miss an opportunity to throw away kernel code). Can anyone point out any obvious reason why this would not work if we consider bulk of the work being plain access filtering? That being said, is there a valid reason why binder is part of device namespace here instead of IPC? -- Janne