From: Christoph Hellwig <hch@infradead.org>
To: Erik Hendriks <hendriks@lanl.gov>
Cc: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: Syscall numbers for BProc
Date: Fri, 4 Apr 2003 20:35:31 +0100 [thread overview]
Message-ID: <20030404203531.A29501@infradead.org> (raw)
In-Reply-To: <20030404193218.GD15620@lanl.gov>; from hendriks@lanl.gov on Fri, Apr 04, 2003 at 12:32:18PM -0700
On Fri, Apr 04, 2003 at 12:32:18PM -0700, Erik Hendriks wrote:
> Is it possible to get a Linux system call number allocated for BProc?
> (http://sourceforge.net/projects/bproc) I've been using arbitrary
> system call numbers for a while but there have been collisions with
> new kernel features. I'd like to avoid that in the future. BProc
> currently works on 2.4.x kernels on x86, alpha and ppc (32bit).
Please explain why you need syscalls and the exact APIs.
next prev parent reply other threads:[~2003-04-04 19:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-04 19:32 Syscall numbers for BProc Erik Hendriks
2003-04-04 19:35 ` Christoph Hellwig [this message]
2003-04-04 20:43 ` hendriks
2003-04-04 21:54 ` H. Peter Anvin
2003-04-05 0:44 ` hendriks
2003-04-05 5:45 ` Christoph Hellwig
2003-04-05 20:15 ` hendriks
2003-04-08 19:19 ` H. Peter Anvin
2003-04-10 6:29 ` Christoph Hellwig
2003-04-14 17:18 ` hendriks
2003-04-14 17:32 ` Richard B. Johnson
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=20030404203531.A29501@infradead.org \
--to=hch@infradead.org \
--cc=hendriks@lanl.gov \
--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