[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m1ipnpl1c9.fsf@fess.ebiederm.org>
Date: Sun, 16 Oct 2011 02:42:14 -0700
From: ebiederm@...ssion.com (Eric W. Biederman)
To: "H. Peter Anvin" <hpa@...or.com>
Cc: "Ted Ts'o" <tytso@....edu>, Kyle Moffett <kyle@...fetthome.net>,
"J. Bruce Fields" <bfields@...ldses.org>,
Matt Helsley <matthltc@...ibm.com>,
Lennart Poettering <mzxreary@...inter.de>,
Kay Sievers <kay.sievers@...y.org>,
linux-kernel@...r.kernel.org, harald@...hat.com, david@...ar.dk,
greg@...ah.com, Linux Containers <containers@...ts.osdl.org>,
"Serge E. Hallyn" <serge@...lyn.com>,
Daniel Lezcano <daniel.lezcano@...e.fr>,
Paul Menage <paul@...lmenage.org>
Subject: Re: Detecting if you are running in a container
"H. Peter Anvin" <hpa@...or.com> writes:
> On 10/14/2011 11:04 AM, Eric W. Biederman wrote:
>>
>> I have found and merged a solution that allows us to name namespaces
>> without needing a namespaces for namespaces.
>>
>
> Something based on UUIDs, perhaps?
>
> UUIDs are kind of exactly this, after all... a single namespace designed
> to be large and random enough to be globally unique without a central
> registration authority.
mount --bind /proc/self/ns/net /var/run/netns/<name>
When we want to refer to the namespace in syscalls we pass a file
descriptor we received from opening the namespace reference object.
That moves the entire naming problem into the file namespace.
Eric
--
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