Hi Eugene,
On 9/11/21 8:29 PM, Eugene Syromyatnikov wrote:
On Sat, Sep 11, 2021 at 6:01 PM Alejandro Colomar
<alx.manpages@xxxxxxxxx> wrote:
Alejandro Colomar (45):
_exit.2: Add LIBRARY section
keyctl.2: Add LIBRARY section
...
socketcall.2: Add LIBRARY section
sigwaitinfo.2: Add LIBRARY section
I'm not sure about these, my understanding is that the primary purpose
of section 2 is syscalls, userspace-kernel interface, and not their
libc wrappers. Even intro(2) states that it is Linux-specific:
“Section 2 of the manual describes the Linux system calls. A system
call is an entry point into the Linux kernel.” Tying it to libc feels
like a bit of a stretch, even though it is the exceedingly common
interface for invoking them.
Thanks for pointing that out. I had some doubts about this in the
beginning. I started writing something like "Linux kernel - GNU C
library" meaning that it's not only a thing of glibc but also the
kernel. But no one replied my RFCs... :/
In the end I simplified it to Standard C library (as FreeBSD does),
because I wasn't convinced of the syntax I had used. And also, since a
man page being in section 2 already implies that it is implemented in
the kernel, I didn't want to be repetitive, and just point what the user
has to link to to make a program work.
There are some system calls that are wrapped by other libraries, such as
keyctl(2) by libkeyutils, and those get a different LIBRARY (you can
check patch 02/45).
But if you think there's a better way to express this, please propose it.
Thanks!
Alex.
--
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/
