From: Michael Kerrisk <mtk.manpages@googlemail.com>
To: lkml <linux-kernel@vger.kernel.org>
Subject: man-pages-3.03 is released
Date: Tue, 08 Jul 2008 17:47:48 +0200 [thread overview]
Message-ID: <48738C24.8020308@gmail.com> (raw)
Gidday
I've released man-pages-3.03.
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
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
The online changelog is available at
http://www.kernel.org/doc/man-pages/changelog.html
(blogged at
http://linux-man-pages.blogspot.com/2008/07/man-pages-303-is-released.html)
and the current version of the pages is browsable at
http://www.kernel.org/doc/man-pages/
An abridged version of the changes in this release that may be of
interest to readers of this list is provided below.
Cheers,
Michael
==================== Changes in man-pages-3.03 ====================
New and rewritten pages
-----------------------
getcpu.2
Andi Kleen, with some text and edits by mtk
Documents the getcpu(2) system call, introduced in Linux 2.6.19.
sched_getcpu.3
mtk
Documents sched_getcpu(3), a wrapper for getcpu(2), provided
since glibc 2.6.
cpuset.7
Paul Jackson, with review and editing by mtk, and comments by
Hidetoshi Seto and Li Zefan
A description of the cpuset file system, the mechanism introduced
kernel 2.6.12 for confining processes to designated processors
and nodes. (Becomes the fourth largest page in man-pages!)
Changes to individual pages
---------------------------
signal.7
mtk
Add a section describing system call restarting, and noting
which system calls are affected by SA_RESTART, and which
system calls are never restarted.
mtk
Describe the aberrant Linux behavior whereby a stop signal
plus SIGCONT can interrupt some system calls, even if no
signal handler has been established, and note the system
calls that behave this way.
reply other threads:[~2008-07-08 15:51 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=48738C24.8020308@gmail.com \
--to=mtk.manpages@googlemail.com \
--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.