From: Rodrigo Ramos <rodrigo.ramos@triforsec.com.br>
To: Robert Love <rml@novell.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: system calls
Date: Mon, 31 Jan 2005 09:04:19 -0300 [thread overview]
Message-ID: <1107173059.12642.8.camel@ZeroOne> (raw)
In-Reply-To: <1107020858.11159.15.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 1099 bytes --]
Hi Robert,
Thank you very much for your help. It really helped me.
When a say groups a mean classes like File Structure, Process Related
and etc. But I already got what I needed... Once again Thank you very
much.
Best Regards,
Rodrigo Ramos
http://www.triforsec.com.br
On Sat, 2005-01-29 at 14:47, Robert Love wrote:
> On Sat, 2005-01-29 at 10:53 -0300, Rodrigo Ramos wrote:
>
> > I would like to know how many groups of system calls are there at Linux
> > 2.4 and 2.6? Where can I find these informations in the Kernel?
>
> I don't know what you mean by groups (a nonempty set G with binary
> operation * s.t. G is associativity, there exists e in G s.t. e*a=a*e=a,
> and there exists i in G s.t. i*b=b*i=e?).
>
> System calls are implemented per-architecture. You can see the list at
> the bottom of arch/i386/kernel/entry.S. There is about 290.
>
> System calls are prefixed by "sys_". Thus, read(2) is implemented in
> the kernel as sys_read(). It, for example, can be found in
> fs/read_write.c.
>
> Hope this helps.
>
> Robert Love
>
>
>
>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2005-01-31 12:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-29 13:53 system calls Rodrigo Ramos
2005-01-29 17:47 ` Robert Love
2005-01-29 18:15 ` Andries Brouwer
2005-01-31 12:04 ` Rodrigo Ramos [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=1107173059.12642.8.camel@ZeroOne \
--to=rodrigo.ramos@triforsec.com.br \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@novell.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