From: Vladimir Zidar <vladimir@mindnever.org>
To: "Randy.Dunlap" <rddunlap@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: system call
Date: 09 Jul 2002 01:59:42 +0200 [thread overview]
Message-ID: <1026172783.2084.26.camel@server1> (raw)
In-Reply-To: <Pine.LNX.4.33L2.0207080808310.7622-100000@dragon.pdx.osdl.net>
On Mon, 2002-07-08 at 17:16, Randy.Dunlap wrote:
> http://www.xenotime.net/linux/syscall_ex/
> contains a howto, kernel patch, and test program.
And how to choose goot syscall number ? Are some numbers pre-reserved
to 'private' syscalls ? What numbers are free to use, without fear that
new kernel release will just jump over them !?
And what about an idea to be able to add syscall by name, from loadab;e
module of course. Userland application will then resolve 'name' to
number at startup, and use it just as ordinary syscall ?
--
Bye,
and have a very nice day !
next prev parent reply other threads:[~2002-07-08 23:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-08 10:15 system call Bruno Pujol
2002-07-08 15:16 ` Randy.Dunlap
2002-07-08 23:59 ` Vladimir Zidar [this message]
2002-07-09 0:13 ` Keith Owens
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=1026172783.2084.26.camel@server1 \
--to=vladimir@mindnever.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
/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