Date: Fri, 20 Dec 2002 13:01:53 -0500 (EST) From: Garrett Wollman <wollman@lcs.mit.edu> To: Juli Mallett <jmallett@FreeBSD.ORG> Cc: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/lib/libc/sys _exit.2 accept.2 access.2 acct.2 adjtime.2 aio_cancel.2 aio_error.2 aio_read.2 aio_return.2 aio_suspend.2 aio_waitcomplete.2 aio_write.2 bind.2 brk.2 chdir Message-ID: <200212201801.gBKI1rdn081991@khavrinen.lcs.mit.edu> In-Reply-To: <20021220012514.A17293@FreeBSD.org> References: <20021219095247.GA79372@sunbay.com> <20021219.211701.128866860.imp@bsdimp.com> <20021220080144.GB70051@sunbay.com> <20021220.010540.103018236.imp@bsdimp.com> <20021220012514.A17293@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
<<On Fri, 20 Dec 2002 01:25:14 -0800, Juli Mallett <jmallett@FreeBSD.ORG> said: > System calls aren't really functions, we just as niceities provide > frontends to system calls that look like C functions to libc consumers. The standards define the C-language binding only, primarily as functional interfaces. How those functional interfaces may resolve to system calls is an implementation detail. Even in FreeBSD we've had some things that either could move, or have moved, across that boundary as implementational demands warranted. The only reason why we still have a separate section 2 of the manual is historical. I wouldn't put any more meaning than that on it. We do not document the actual system calls (see, for example, how pipe() and vfork() are implemented), but only the C-language functional interface. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200212201801.gBKI1rdn081991>