From: viro@parcelfarce.linux.theplanet.co.uk
To: David Howells <dhowells@warthog.cambridge.redhat.com>
Cc: David Howells <dhowells@redhat.com>,
Linus Torvalds <torvalds@transmeta.com>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] VFS autmounter support v2
Date: Thu, 19 Jun 2003 15:55:54 +0100 [thread overview]
Message-ID: <20030619145554.GF6754@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <3283.1056016010@warthog.warthog>
On Thu, Jun 19, 2003 at 10:46:50AM +0100, David Howells wrote:
> Besides, going back to your original argument, I think you make an invalid
> assertion:
>
> Namespaces are completely unrelated - I have them set for two
> different users that happen to need some common files, but otherwise
> have very different environments.
>
> They are not quite completely unrelated. The only way (or so it seems) to get
> a new namespace is to derive one by way of CLONE_NS. This clones the namespace
> of the parent, and so the child's namespace then should have all the features
> of the parent's namespace _UNTIL_ at such time the child or one of its
> descendents rearranges the topology!
And how the fuck do you "rearrange topology" with your patch?!?
next prev parent reply other threads:[~2003-06-19 14:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-18 14:20 David Howells
2003-06-18 20:59 ` viro
2003-06-19 9:46 ` David Howells
2003-06-19 14:55 ` viro [this message]
[not found] <fa.nerig52.1j7u3qk@ifi.uio.no>
[not found] ` <fa.fq0dsjb.1a06mop@ifi.uio.no>
2003-06-19 14:00 ` Mike Waychison
2003-06-19 14:31 ` David Howells
2003-06-19 15:13 ` Mike Waychison
2003-06-19 15:34 ` viro
2003-06-19 16:53 ` 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=20030619145554.GF6754@parcelfarce.linux.theplanet.co.uk \
--to=viro@parcelfarce.linux.theplanet.co.uk \
--cc=dhowells@redhat.com \
--cc=dhowells@warthog.cambridge.redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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
all inboxes | Powered by JetHome®