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