From: Robert Love <rml@tech9.net>
To: Pavel Machek <pavel@suse.cz>
Cc: Marcelo Tosatti <marcelo@conectiva.com.br>,
lkml <linux-kernel@vger.kernel.org>,
viro@math.psu.edu
Subject: Re: Linux 2.4.19-pre6
Date: 07 Apr 2002 19:16:33 -0400 [thread overview]
Message-ID: <1018221403.913.134.camel@phantasy> (raw)
In-Reply-To: <20020407163026.G46@toy.ucw.cz>
On Sun, 2002-04-07 at 12:30, Pavel Machek wrote:
> > <viro@math.psu.edu> (02/04/01 1.322)
> > turns (mount_sem,vfsmntlist,root_vfsmnt) into per-process object
> >
> > <viro@math.psu.edu> (02/04/01 1.323)
> > makes /proc/mounts a symlink to /proc/<pid>/mounts.
>
> I don't see how this could be considered bugfix. Seems like new feature to
> me, and dangerous one, too.
It isn't a bugfix, it is a new feature - and I am generally against new
things in 2.4 like this but it is a pretty sane one. Further it has
seen testing in 2.5 and is without a doubt stable.
The new semantics are such that applications inherit from their parent
their namespace, so if user code is not changed everything is the same
to applications.
Oh, and Al knows what he is doing.
Robert Love
prev parent reply other threads:[~2002-04-07 23:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-05 5:00 Linux 2.4.19-pre6 Marcelo Tosatti
2002-04-05 10:54 ` Linux 2.4.19-pre6 doesn't compile on Alpha Jurriaan on Alpha
2002-04-05 11:48 ` Alexander Viro
2002-04-05 12:46 ` Linux 2.4.19-pre6 doesn't compile on Alpha and sparc64 Jurgen Philippaerts
2002-04-05 13:02 ` Jurgen Philippaerts
2002-04-05 13:07 ` David S. Miller
2002-04-07 16:30 ` Linux 2.4.19-pre6 Pavel Machek
2002-04-07 23:16 ` Robert Love [this message]
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=1018221403.913.134.camel@phantasy \
--to=rml@tech9.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=pavel@suse.cz \
--cc=viro@math.psu.edu \
/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