Re: [Devel] [RFC] [PATCH 2/2] namespace enter: introduce sys_hijack (v3)

2007-09-10 Thread Serge E. Hallyn
Quoting Paul Menage ([EMAIL PROTECTED]): > On 9/4/07, Serge E. Hallyn <[EMAIL PROTECTED]> wrote: > > We could of course have the ns_container subsystem do that. The > > ns_container generally stick around until the admin does a manual rm on > > its directory, so this way we could keep the nsproxy

Re: [Devel] [RFC] [PATCH 2/2] namespace enter: introduce sys_hijack (v3)

2007-09-05 Thread Paul Menage
On 9/4/07, Serge E. Hallyn <[EMAIL PROTECTED]> wrote: > We could of course have the ns_container subsystem do that. The > ns_container generally stick around until the admin does a manual rm on > its directory, so this way we could keep the nsproxy around. So how about taking sys_hijack() even fu

Re: [Devel] [RFC] [PATCH 2/2] namespace enter: introduce sys_hijack (v3)

2007-09-04 Thread Serge E. Hallyn
Quoting Dave Hansen ([EMAIL PROTECTED]): > On Tue, 2007-09-04 at 07:50 -0500, Serge E. Hallyn wrote: > > > What do you do if there are no processes in a particular container? > > > > The nsproxy will have been released so you couldn't enter it anyway. > > Yeah, we'd need some kind of other objec

Re: [Devel] [RFC] [PATCH 2/2] namespace enter: introduce sys_hijack (v3)

2007-09-04 Thread Dave Hansen
On Tue, 2007-09-04 at 07:50 -0500, Serge E. Hallyn wrote: > > What do you do if there are no processes in a particular container? > > The nsproxy will have been released so you couldn't enter it anyway. Yeah, we'd need some kind of other object to keep the nsproxy around and hold a reference to

Re: [Devel] [RFC] [PATCH 2/2] namespace enter: introduce sys_hijack (v3)

2007-09-04 Thread Serge E. Hallyn
Quoting Paul Menage ([EMAIL PROTECTED]): > On 8/29/07, Serge E. Hallyn <[EMAIL PROTECTED]> wrote: > > >From aec05999084bf3a94add66e98462652ed9408f86 Mon Sep 17 00:00:00 2001 > > From: [EMAIL PROTECTED] <[EMAIL PROTECTED]> > > Date: Wed, 22 Aug 2007 15:03:57 -0700 > > Subject: [RFC] [PATCH 2/2] name

Re: [Devel] [RFC] [PATCH 2/2] namespace enter: introduce sys_hijack (v3)

2007-09-03 Thread Paul Menage
On 8/29/07, Serge E. Hallyn <[EMAIL PROTECTED]> wrote: > >From aec05999084bf3a94add66e98462652ed9408f86 Mon Sep 17 00:00:00 2001 > From: [EMAIL PROTECTED] <[EMAIL PROTECTED]> > Date: Wed, 22 Aug 2007 15:03:57 -0700 > Subject: [RFC] [PATCH 2/2] namespace enter: introduce sys_hijack (v3) > > Introduc

[Devel] [RFC] [PATCH 2/2] namespace enter: introduce sys_hijack (v3)

2007-08-29 Thread Serge E. Hallyn
>From aec05999084bf3a94add66e98462652ed9408f86 Mon Sep 17 00:00:00 2001 From: [EMAIL PROTECTED] <[EMAIL PROTECTED]> Date: Wed, 22 Aug 2007 15:03:57 -0700 Subject: [RFC] [PATCH 2/2] namespace enter: introduce sys_hijack (v3) Introduce sys_hijack (for x86 only). It is like clone, but in place of a