linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: "libc-alpha@sourceware.org" <libc-alpha@sourceware.org>,
	linux-man <linux-man@vger.kernel.org>
Cc: mtk.manpages@gmail.com, Andrew Josey <ajosey@opengroup.org>,
	Ruediger Oertel <ro@suse.de>, Petr Gajdos <PGajdos@suse.cz>,
	Jan Haloup <jchaloup@redhat.com>,
	Ingo Schwarze <schwarze@usta.de>,
	"Dr. Tobias Quathamer" <toddy@debian.org>,
	Andries Brouwer <Andries.Brouwer@cwi.nl>,
	Felix Janda <felix.janda@posteo.de>,
	Andy Kluger <AndyKluger@gmail.com>,
	Daniel Lublin <daniel@lublin.se>,
	Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: POSIX.1-2017 manual pages for Linux
Date: Thu, 5 Nov 2020 14:18:46 +0100	[thread overview]
Message-ID: <0a36ce05-f3f3-afd5-7675-a5fc4b4f0c02@gmail.com> (raw)

Hello all,

The manual pages produced by the Linux man-pages project attempt
to document deviations between Linux behavior and the POSIX.1 standard.
However, the pages are no substitute for the standard itself.

In 2004 and 2014, the IEEE and The Open Group decided to grant
permission to the Linux man-pages project to distribute parts of the
then-current version of POSIX.1 in manual page format. That decision
provided an extremely valuable resource for Linux programmers who wanted
to write applications that are portable across UNIX systems.

We are pleased to announce that, once again, the IEEE and The Open Group
have kindly granted us permission to distribute extracts from the latest
version of the POSIX.1 standard:

    IEEE Std 1003.1-2017, Standard for Information Technology--Portable
    Operating System Interface (POSIX), The Open Group Base Specifications
    Issue 7, 2018 Edition, Copyright (C) 2018 by the Institute of
    Electrical and Electronics Engineers, Inc and The Open Group.

(For those curious about the "2017" designation, this is
POSIX.1-2008 with the 2013 Technical Corrigendum 1 and the
2016 Technical Corrigendum 2 applied.)

Once again using the excellent scripts of Felix Janda, the source
files supplied by IEEE and The Open Group have been cleanly converted
to  "man" format. The result is that portions of the standard are
made available for easy reference  as (1139!) manual pages. Those
pages are divided into three sections:

    Section 0p = POSIX headers (specifications for header files)
    Section 1p = POSIX utilities (i.e., specifications shell commands)
    Section 3p = POSIX functions (specifications for functions)

Tarballs containing the pages can be found at
https://www.kernel.org/pub/linux/docs/man-pages/man-pages-posix/man-pages-posix-2017-a.tar.gz
and
https://www.kernel.org/pub/linux/docs/man-pages/man-pages-posix/man-pages-posix-2017-a.tar.xz

Please note that all pages carry the following disclaimer:

    In the event of any discrepancy between this version and the original
    IEEE and The Open Group Standard, the original IEEE and The Open
    Group Standard is the referee document. The original Standard can
    be obtained online at http://www.opengroup.org/unix/online.html .

    Any typographical or formatting errors that appear in this page are
    most likely to have been introduced during the conversion of the
    source files to man page format. To report such errors, see
    https://www.kernel.org/doc/man-pages/reporting_bugs.html .

Regarding the last paragraph, a few widespread typographical issues
that resulted during the conversion of the previous (2014) version
of the POSIX manual pages should hopefully be fixed in this release.

Thanks,

Michael

-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/

                 reply	other threads:[~2020-11-05 13:21 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=0a36ce05-f3f3-afd5-7675-a5fc4b4f0c02@gmail.com \
    --to=mtk.manpages@gmail.com \
    --cc=Andries.Brouwer@cwi.nl \
    --cc=AndyKluger@gmail.com \
    --cc=PGajdos@suse.cz \
    --cc=ajosey@opengroup.org \
    --cc=daniel@lublin.se \
    --cc=felix.janda@posteo.de \
    --cc=jchaloup@redhat.com \
    --cc=konstantin@linuxfoundation.org \
    --cc=libc-alpha@sourceware.org \
    --cc=linux-man@vger.kernel.org \
    --cc=ro@suse.de \
    --cc=schwarze@usta.de \
    --cc=toddy@debian.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;
as well as URLs for NNTP newsgroup(s).