From: Michael Kerrisk <mtk-manpages@gmx.net>
To: lkml <linux-kernel@vger.kernel.org>
Subject: man-pages-2.57 is released
Date: Sat, 16 Jun 2007 14:31:46 +0200 [thread overview]
Message-ID: <4673D832.8060009@gmx.net> (raw)
Gidday,
I just released man-pages-2.57.
This release is now available for download at:
http://www.kernel.org/pub/linux/docs/manpages
or ftp://ftp.kernel.org/pub/linux/docs/manpages
and soon at:
ftp://ftp.win.tue.nl/pub/linux-local/manpages
Various things remain to be fixed in man-pages. A few of the outstanding
FIXME points from section 2 are listed below. Any assistance with these
points would be most welcome.
Cheers,
Michael
(man-pages maintenance is supported by Google, as a Google engineer 20%
project.)
==========
./man2/ioperm.2
FIXME is the following ("Only the first 0x3ff I/O ports can be
specified in this manner") still true? Looking at changes in
include/asm-i386/processor.h between 2.4 and 2.6 suggests
that the limit is different in 2.6.
==========
./man2/mprotect.2
FIXME
Document PROT_GROWSUP and PROT_GROWSDOWN
==========
./man2/nfsservctl.2
FIXME The description of nfsservctl() on this page
is woefully thin.
==========
./man2/shmop.2
FIXME A good explanation of the rationale for the existence
of SHMLBA would be useful here
--
Michael Kerrisk
maintainer of Linux man pages Sections 2, 3, 4, 5, and 7
Want to help with man page maintenance? Grab the latest tarball at
http://www.kernel.org/pub/linux/docs/manpages/
read the HOWTOHELP file and grep the source files for 'FIXME'.
next reply other threads:[~2007-06-17 14:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-16 12:31 Michael Kerrisk [this message]
[not found] <8x3Cc-1LD-13@gated-at.bofh.it>
2007-06-18 14:06 ` man-pages-2.57 is released Bodo Eggert
2007-06-18 15:01 ` Michael Kerrisk
2007-06-18 18:00 ` H. Peter Anvin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4673D832.8060009@gmx.net \
--to=mtk-manpages@gmx.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.