From: "Serge E. Hallyn" <hallyn@CS.WM.EDU>
To: Ram Pai <linuxram@us.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: per-process namespace?
Date: Wed, 30 Jun 2004 20:14:42 -0400 [thread overview]
Message-ID: <20040701001442.GA28099@escher.cs.wm.edu> (raw)
In-Reply-To: <1088619320.2927.77.camel@localhost.localdomain>
> The per-process namespace concept comes in handy here except for the
> static nature of the namespace. In the sense, any changes to the system
> namespace do not reflect in the children namespace.
Static?
It's not static! It's private, as advertised.
It sounds like you're asking (or your customer is asking) for
copy-on-write namespaces :)
next prev parent reply other threads:[~2004-07-01 0:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-29 18:47 per-process namespace? Ram Pai
2004-06-29 21:10 ` Mike Waychison
2004-06-29 22:10 ` viro
2004-06-29 23:22 ` Ram Pai
2004-06-30 13:15 ` Mike Waychison
2004-06-30 18:15 ` Ram Pai
2004-07-01 0:14 ` Serge E. Hallyn [this message]
2004-07-01 1:32 ` Ram Pai
2004-06-29 22:25 ` Ram Pai
2004-06-30 13:30 ` Mike Waychison
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=20040701001442.GA28099@escher.cs.wm.edu \
--to=hallyn@cs.wm.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxram@us.ibm.com \
/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