From mboxrd@z Thu Jan 1 00:00:00 1970 From: "warron.french" Subject: Syscalls and associated purpose defined Date: Thu, 9 Feb 2017 18:58:16 -0500 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2889700292262962152==" Return-path: Received: from mx1.redhat.com (ext-mx06.extmail.prod.ext.phx2.redhat.com [10.5.110.30]) by int-mx14.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id v19NwJ16009897 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Thu, 9 Feb 2017 18:58:19 -0500 Received: from mail-qk0-f180.google.com (mail-qk0-f180.google.com [209.85.220.180]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id F40873DBDA for ; Thu, 9 Feb 2017 23:58:18 +0000 (UTC) Received: by mail-qk0-f180.google.com with SMTP id s140so22803411qke.0 for ; Thu, 09 Feb 2017 15:58:17 -0800 (PST) List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-audit-bounces@redhat.com Errors-To: linux-audit-bounces@redhat.com To: linux-audit@redhat.com List-Id: linux-audit@redhat.com --===============2889700292262962152== Content-Type: multipart/alternative; boundary=001a114906f4456a04054821c164 --001a114906f4456a04054821c164 Content-Type: text/plain; charset=UTF-8 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%20reference.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. Thanks, -------------------------- Warron French --001a114906f4456a04054821c164 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
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,=C2=A0http:= //www.digilife.be/quickreferences/qrc/linux%20system%20call%20quick%20refer= ence.pdf, but it is not up to date and doesn't really define the sy= stem call's purpose - at least to my level of understanding.
=

Thanks,
--------------------------
Warron French
=
--001a114906f4456a04054821c164-- --===============2889700292262962152== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline --===============2889700292262962152==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steve Grubb Subject: Re: Syscalls and associated purpose defined Date: Thu, 09 Feb 2017 19:11:17 -0500 Message-ID: <2791816.vlPMi4BfQj@x2> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-audit-bounces@redhat.com Errors-To: linux-audit-bounces@redhat.com To: linux-audit@redhat.com List-Id: linux-audit@redhat.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