From: Michael Kerrisk <mtk-manpages@gmx.net>
To: lkml <linux-kernel@vger.kernel.org>
Subject: man-pages-2.40 is released
Date: Wed, 11 Oct 2006 11:48:58 +0200 [thread overview]
Message-ID: <452CBE0A.9050300@gmx.net> (raw)
Gidday,
I recently released man-pages-2.40.
This release is now available for download at:
ftp://ftp.win.tue.nl/pub/linux-local/manpages
and soon at:
ftp://ftp.kernel.org/pub/linux/docs/manpages
or mirrors: ftp://ftp.XX.kernel.org/pub/linux/docs/manpages
Changes in this release that may be of interest to readers
of this list include the following:
Changes to individual pages
---------------------------
execve.2
mtk
Added list of process attributes that are not preserved on exec().
fork.2
mtk, after a suggestion by Christoph Hellwig
Greatly expanded, to describe all attributes that differ
in parent and child.
linkat.2
mtk
Document AT_SYMLINK_FOLLOW (new in 2.6.18).
proc.5
Chuck Ebbert
Document /proc/PID/auxv.
Cheers,
Michael
--
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'.
reply other threads:[~2006-10-11 9:45 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=452CBE0A.9050300@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox