|| ||"Michael Kerrisk" <email@example.com>|
|| ||man-pages-2.29 is released|
|| ||Sat, 8 Apr 2006 23:07:36 +0200 (MEST)|
I recently released man-pages-2.29, which can be found at the
location in the .sig. A list of some notable changes can be found
further down in this message
*** A request ***
Manual pages for the follwoing system calls are notably absent
from the man-pages set. Contributions would be most welcome.
add_key(2) (new in kernel 2.6.10)
keyctl(2) (new in kernel 2.6.10)
request_key(2) (new in kernel 2.6.10)
ioprio_get(2) (new in kernel 2.6.13)
ioprio_set(2) (new in kernel 2.6.13)
restart_syscall(2) (new in kernel 2.6)
kexec_load(2) (new in kernel 2.6.13)
migrate_pages(2) (new in kernel 2.6.16)
Changes in this release that may be of interest to readers
of this list include the following:
New page describing mkdirat(2), new in 2.6.16.
New page describing mknodat(2), new in 2.6.16.
New page describing core dump files.
New page describing mkfifoat(3).
Changes to individual pages
Added BUGS text on 2.6.x handling of RLIMIT_CPU limit
of zero seconds. See
The man-pages set contains sections 2, 3, 4, 5, and 7 of
the manual pages. These sections describe the following:
2: (Linux) system calls
3: (libc) library functions
5: File formats and protocols
7: Overview pages, conventions, etc.
As far as this list is concerned the most relevant parts are:
all of sections 2 and 4, which describe kernel-userland interfaces;
in section 5, the proc(5) manual page, which attempts (it's always
catching up) to be a comprehensive description of /proc; and
various pages in section 7, some of which are overview pages of
kernel features (e.g., networking protocols).
If you make a change to a kernel-userland interface, or observe
a discrepancy between the manual pages and reality, would you
please send me (at firstname.lastname@example.org ) one of the following
(in decreasing order of preference):
1. An in-line "diff -u" patch with text changes for the
corresponding manual page. (The most up-to-date version
of the manual pages can always be found at
2. Some raw text describing the changes, which I can then
integrate into the appropriate manual page.
3. A message alerting me that some part of the manual pages
does not correspond to reality. Eventually, I will try to
remedy the situation.
Obviously, as we get further down this list, more of my time
is required, and things may go slower, especially when the
changes concern some part of the kernel that I am ignorant
about and I can't find someone to assist.
maintainer of Linux man pages Sections 2, 3, 4, 5, and 7
Want to help with man page maintenance?
Grab the latest tarball at
read the HOWTOHELP file and grep the source
files for 'FIXME'.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/