Subject: Re: Syscall and syscall versioning documentation
To: None <firstname.lastname@example.org>
From: Pavel Cahyna <email@example.com>
Date: 11/21/2006 23:16:24
On Tue, Nov 21, 2006 at 06:15:37PM +0000, Christos Zoulas wrote:
> In article <20061120210855.GA29417@NetBSD.org>,
> Pavel Cahyna <pavel@NetBSD.org> wrote:
> >I've finally committed that, after changing it a bit according to
> >numerous suggestions from Emmanuel Dreyfus. Improvements are welcome.
> 1. Why not use ansi prototypes to simplify the formatting?
I've used Docbook prototypes. If another formatting is desired, it should
be done by altering the templates.
> 2. In 3.2.3, show the compat_30_sys_sockets_args structure and explain
> the SCARG() macro.
> 3. In 3.2.6, mention that we usually implement the older version of the
> syscall in libc so that we can provide binary compatibility for
> dynamically linked libraries without needing the kernel support.
This was already there.
> Also mention that we don't litter the code with compat defines,
> but we put stuff in lib/libc/compat or sys/compat.
> Mention how __RENAME() works and the __LIBC12_SOURCE__ define.
I've mentioned what __RENAME does but now how it works, because its user
should not care.