From: Andries Brouwer <aebr@win.tue.nl>
To: Robert Love <rml@novell.com>
Cc: Rodrigo Ramos <rodrigo.ramos@triforsec.com.br>,
linux-kernel@vger.kernel.org
Subject: Re: system calls
Date: Sat, 29 Jan 2005 19:15:18 +0100 [thread overview]
Message-ID: <20050129181518.GG6010@pclin040.win.tue.nl> (raw)
In-Reply-To: <1107020858.11159.15.camel@localhost>
On Sat, Jan 29, 2005 at 12:47:38PM -0500, Robert Love wrote:
> System calls are prefixed by "sys_". Thus, read(2) is implemented in
> the kernel as sys_read().
Now that you say this - of course you know that the actual
situation is much more messy. Sometimes I wonder whether
it would be useful to make such a statement more true
and for example change sys_olduname, sys_uname, sys_newuname
into sys_oldolduname, sys_olduname, sys_uname.
Andries
next prev parent reply other threads:[~2005-01-29 18:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-29 13:53 Rodrigo Ramos
2005-01-29 17:47 ` Robert Love
2005-01-29 18:15 ` Andries Brouwer [this message]
2005-01-31 12:04 ` Rodrigo Ramos
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=20050129181518.GG6010@pclin040.win.tue.nl \
--to=aebr@win.tue.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@novell.com \
--cc=rodrigo.ramos@triforsec.com.br \
/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
all inboxes | Powered by JetHome®