man-pages-3.03 is released

[Michael Kerrisk]

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.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/