From: Michael Kerrisk <mtk.manpages@googlemail.com>
To: lkml <linux-kernel@vger.kernel.org>
Subject: man-pages-3.23 is released
Date: Sat, 3 Oct 2009 08:06:32 +0200 [thread overview]
Message-ID: <cfd18e0f0910022306x2b5fd7ccief4422b145ef051e@mail.gmail.com> (raw)
Gidday,
I've released man-pages-3.23.tar.gz - man pages for Linux
This release is now available for download at:
http://www.kernel.org/pub/linux/docs/man-pages
or ftp://ftp.kernel.org/pub/linux/docs/man-pages
man-pages nowadays also has a public git repository at
git://git.kernel.org/pub/scm/docs/man-pages/man-pages.git
The online changelog is available at
http://www.kernel.org/doc/man-pages/changelog.html
(blogged at
http://linux-man-pages.blogspot.com/2009/10/man-pages-323-release-my-book.html )
and the current version of the pages is browsable at
http://www.kernel.org/doc/man-pages/
This release consists entirely of fixes to existing pages. An abridged
list changes that may be of interest to readers of this list is
provided below.
Cheers,
Michael
==================== Changes in man-pages-3.23 ====================
Released: 2009-09-30, Munich
getrusage.2
Michael Kerrisk
ru_inblock and ru_oublock are now implemented
These fields of the rusage structure are filled in since
Linux 2.6.22.
mmap.2
Michael Kerrisk
Add brief documentation of MAP_HUGETLB
This flag is new in 2.6.32, and serves a similar
purpose to the shmget() SHM_HUGETLB flag.
open.2
Christoph Hellwig
add some comments on O_SYNC and friends
splice.2
tee.2
vmsplice.2
Mark Hills
Fix return type
Since glibc 2.7, the return type for these functions
is ssize_t (formerly it was long).
mq_overview.7
Michael Kerrisk
Change documented ranges for msg_max and msgsize_max
Linux 2.6.28 changed the permissible ranges for
these /proc files.
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Author of "The Linux Programming Interface" http://blog.man7.org/
reply other threads:[~2009-10-03 6:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=cfd18e0f0910022306x2b5fd7ccief4422b145ef051e@mail.gmail.com \
--to=mtk.manpages@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®