man-pages-2.44 is released

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Gidday,

After a long hiatus, a new man-pages release...

And a happy announcement!  My work on man-pages is now partially supported
by my employer, Google.  Henceforth, something up to 20% [*] of my working
week (depending on other time pressures...) will be spent on man-pages
maintenance.  Thanks, Google!

So...

I've released man-pages-2.44.

This release is now available for download at:

    ftp://ftp.kernel.org/pub/linux/docs/manpages
    or mirrors: ftp://ftp.XX.kernel.org/pub/linux/docs/manpages

and soon at:

    ftp://ftp.win.tue.nl/pub/linux-local/manpages

Cheers,

Michael

[*] http://www.google.com/support/jobs/bin/static.py?page=about.html
http://en.wikipedia.org/wiki/Google#.22Twenty_percent.22_time

=======

This release contains a very large number of changes.  Among the changes
that may be of interest to readers of this list are the following:

New pages
---------

termio.7
    mtk, after a bit of prodding by Reuben Thomas
        A brief discussion of the old System V termio interface,
        with pointers to pages that will contain the information
        that the reader probably wants.

Changes to individual pages
---------------------------

access.2
    mtk
        Since 2.6.20, access() honours the MS_NOEXEC mount flag.

mincore.2
    Nick Piggin
        Kernel 2.6.21 fixes several earlier bugs in mincore().
    mtk
        Rewrote various parts to make the page clearer.

mmap.2
    mtk
        Rewrote and reorganised various parts to be clearer.

mount.2
    mtk / Val Henson
        Document MS_RELATIME, new in Linux 2.6.20.

semop.2
    mtk
        If sops contains multiple operations, then these are performed
        in array order.  All Unix systems that I know of do this,
        and some Linux applications depend on this behaviour.  SUSv3
        made no explicit statement here, but SUSv4 will explicitly
        require this behaviour.

ptrace.2
    Chuck Ebbert
        When the parent receives an event with PTRACE_EVENT_* set,
        the child is not in the normal signal delivery path.  This
        means the parent cannot do ptrace(PTRACE_CONT) with a signal
        or ptrace(PTRACE_KILL).  kill() with a SIGKILL signal can be
        used instead to kill the child process after receiving one
        of these messages.

time.7
    mtk
        Since kernel 2.6.20, the software clock can also be 300 HZ.


-- 
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'.

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

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux