From: Steve Grubb <sgrubb@redhat.com>
To: linux-audit@redhat.com
Subject: Re: Syscalls and associated purpose defined
Date: Thu, 09 Feb 2017 19:11:17 -0500 [thread overview]
Message-ID: <2791816.vlPMi4BfQj@x2> (raw)
In-Reply-To: <CAJdJdQmwNKuSZDoO+D4iUT=0ZCze-wGBfecX2uDoC9LhwzoaGQ@mail.gmail.com>
On Thursday, February 9, 2017 6:58:16 PM EST warron.french wrote:
> Does anyone know of an up-to-date document on Linux system calls and their
> associated purposes defined (in plain English)?
>
> For example, defining *unlink *and *unlinkat*?
>
> I found this document,
> http://www.digilife.be/quickreferences/qrc/linux%20system%20call%20quick%20r
> eference.pdf, but it is not up to date and doesn't really define the system
> call's purpose - at least to my level of understanding.
We have always considered the man pages to be the ultimate source of
information. You may have use the number 2 occassinally when there are
programs with the same name. For example, "man 2 write".
-Steve
prev parent reply other threads:[~2017-02-10 0:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 23:58 Syscalls and associated purpose defined warron.french
2017-02-10 0:11 ` Steve Grubb [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=2791816.vlPMi4BfQj@x2 \
--to=sgrubb@redhat.com \
--cc=linux-audit@redhat.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