| |||||||||||||
Glibc and the kernel user-space APIGlibc and the kernel user-space APIPosted Feb 1, 2013 6:17 UTC (Fri) by vapier (subscriber, #15768)In reply to: Glibc and the kernel user-space API by paulj Parent article: Glibc and the kernel user-space API
section 2 is the standard location for syscalls (or rather, for the ABI the kernel provides). but the contention isn't the location, it's splitting information across two pages for end developers (section 2 and section 3). mkerrisk posted a link that explains a bit more.
(Log in to post comments)
Glibc and the kernel user-space API Posted Feb 1, 2013 11:37 UTC (Fri) by paulj (subscriber, #341) [Link]
I'm aware what sections 2 and 3 are traditionally for. However, you can have "sub-sections", indicated by a letter suffix on the section. E.g. several sections have POSIX specific sub-sections. Compare "man 1 sh" to "man 1p sh", or "man nan" to "man 3p nan".
There's no reason you couldn't have a "k" sub-section (so "2k" and/or "3k"), to document kernel specific things about programming interfaces. There's no reason why you can't have *both* a glibc and Linux kernel specific version for a man-page.
Glibc and the kernel user-space API Posted Feb 2, 2013 22:19 UTC (Sat) by vapier (subscriber, #15768) [Link]
using subsections instead of the proper (and already standardized) main sections doesn't address the stated concern in any way
|
|||||||||||||