From: Alejandro Colomar <alx@kernel.org>
To: Ole Wiedemann <wiedemann@cs.fau.de>
Cc: austin-group-permissions@opengroup.org,
linux-man@vger.kernel.org, Andrew Josey <ajosey@opengroup.org>,
Geoff Clare <gwc@opengroup.org>, Eric Blake <eblake@redhat.com>,
Brian Inglis <Brian.Inglis@shaw.ca>,
"G. Branden Robinson" <g.branden.robinson@gmail.com>,
Michael Kerrisk <mtk.manpages@gmail.com>
Subject: Re: Question about the availability of POSIX 2024 man pages
Date: Fri, 23 Jan 2026 15:36:32 +0100 [thread overview]
Message-ID: <aXODRzxM431LVqkD@devuan> (raw)
In-Reply-To: <6a5f52e4-f7e4-4d7e-9f4b-3c10722904a4@cs.fau.de>
[-- Attachment #1: Type: text/plain, Size: 1388 bytes --]
[CC += linux-man@, austin-group-permissions@, and a few interested people]
On Fri, Jan 23, 2026 at 11:53:08AM +0100, Ole Wiedemann wrote:
> Dear Mr. Colomar,
Hello Ole,
> We are currently overseeing a university course on systems programming that
> uses the POSIX 2008 interfaces. There are some interfaces in the newer POSIX
> 2024 specifications that we would like to use, as they eliminate some common
> pitfalls. However, there are seemingly no man pages anywhere for the newer
> standard.
>
> Thus I wanted to ask kindly if you have any idea when (or if) man pages for
> POSIX 2024 will be available?
Currently, there are no POSIX.1-2024 manual pages.
The main problem is that the POSIX sources are not public. Michael, the
previous maintainer, had agreed (AFAIK) with POSIX to receive privately
a copy of POSIX (I don't know in which format; IIRC, it was HTML?), and
then run them through a script to produce the published POSIX manual
pages. I find the burden of that to be too excessive.
If POSIX makes their roff sources public (preferably, in a git
repository) (not necessarily under a free software license, but publicly
readable), I'd be happy to work with those. That depends on the
Copyright holders (IEEE and the Open Group).
> Kind regards,
> Ole Wiedemann
Have a lovely day!
Alex
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
parent reply other threads:[~2026-01-23 14:36 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <6a5f52e4-f7e4-4d7e-9f4b-3c10722904a4@cs.fau.de>]
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=aXODRzxM431LVqkD@devuan \
--to=alx@kernel.org \
--cc=Brian.Inglis@shaw.ca \
--cc=ajosey@opengroup.org \
--cc=austin-group-permissions@opengroup.org \
--cc=eblake@redhat.com \
--cc=g.branden.robinson@gmail.com \
--cc=gwc@opengroup.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=wiedemann@cs.fau.de \
/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.