From: Marko Kreen <marko@l-t.ee>
To: Alexander Viro <viro@math.psu.edu>
Cc: Andries.Brouwer@cwi.nl, aeb@veritas.com, linux-kernel@vger.kernel.org
Subject: Re: [patch] Re: [patch-2.4.0-test12-pre6] truncate(2) permissions
Date: Fri, 8 Dec 2000 13:25:53 +0200 [thread overview]
Message-ID: <20001208132553.C5744@l-t.ee> (raw)
In-Reply-To: <UTC200012080235.DAA157231.aeb@aak.cwi.nl> <Pine.GSO.4.21.0012072156420.22281-100000@weyl.math.psu.edu>
In-Reply-To: <Pine.GSO.4.21.0012072156420.22281-100000@weyl.math.psu.edu>; from viro@math.psu.edu on Thu, Dec 07, 2000 at 09:59:18PM -0500
On Thu, Dec 07, 2000 at 09:59:18PM -0500, Alexander Viro wrote:
> On Fri, 8 Dec 2000 Andries.Brouwer@cwi.nl wrote:
> > > BTW, could we finally lose mpx(2)?
> >
> > Maybe we lost it - I find sys_mpx only in a comment in arch/arm/kernel/calls.S
>
> Sure, but man2/mpx.2 is alive and well...
manpages-dev 1.31-1 of debian:
$ ll /usr/share/man/man2/mpx.2.gz
... /usr/share/man/man2/mpx.2.gz -> unimplemented.2.gz
$ man 2 mpx
NAME
afs_syscall, break, ftime, gtty, lock, mpx, phys, prof,
profil, stty, ulimit - unimplemented system calls
--
marko
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-08 11:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-08 2:35 [patch] Re: [patch-2.4.0-test12-pre6] truncate(2) permissions Andries.Brouwer
2000-12-08 2:59 ` Alexander Viro
2000-12-08 11:25 ` Marko Kreen [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-12-06 22:38 Alexander Viro
2000-12-07 10:18 ` [patch] " Tigran Aivazian
2000-12-07 10:53 ` Tigran Aivazian
2000-12-07 13:23 ` Alexander Viro
2000-12-07 13:48 ` Tigran Aivazian
2000-12-07 15:03 ` Tigran Aivazian
2000-12-07 15:24 ` Alexander Viro
2000-12-07 16:16 ` Andries Brouwer
2000-12-07 22:15 ` Alexander Viro
2000-12-07 16:06 ` Andries Brouwer
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=20001208132553.C5744@l-t.ee \
--to=marko@l-t.ee \
--cc=Andries.Brouwer@cwi.nl \
--cc=aeb@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.