All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Seth McDonald <sethmcmail@pm.me>
Cc: Collin Funk <collin.funk1@gmail.com>,
	 "linux-man@vger.kernel.org" <linux-man@vger.kernel.org>
Subject: Re: Early POSIX versions seldom included in history sections
Date: Tue, 23 Dec 2025 13:43:56 +0100	[thread overview]
Message-ID: <aUqNNsf3ygIj0mxI@devuan> (raw)
In-Reply-To: <SsdGy_ZRyWESN5bZIDs6LXPW-oM7QbWpFa6AWUcX700C7u81iGXJPEatWc0ilPwOHnh4Dq8edSz_D7i-2Ti0iLi0ttFY2BoaYyw6yUjdmTU=@pm.me>

[-- Attachment #1: Type: text/plain, Size: 2183 bytes --]

Hi Seth,

On Tue, Dec 23, 2025 at 03:56:23AM +0000, Seth McDonald wrote:
> > > SUSv2.
> > > POSIX.1-2001 (XSI).
> > > POSIX.1-2008.
> 
> I do believe the standards(7) man page does describe these standards,
> including XSI. From the POSIX.1-2001/SUSv3 section:
> 
> 'The standard defines two levels of conformance: POSIX conformance,
> which is a baseline set of interfaces required of a conforming system;
> and XSI Conformance, which additionally mandates a set of interfaces
> (the "XSI extension") which are only optional for POSIX conformance.
> XSI-conformant systems can be branded UNIX 03.'
> 
> That said, I can certainly understand how just listing a bunch of
> acronyms and numbers (SUSv2, POSIX.1-2001 XSI, POSIX.1-2008) would be
> confusing for many not familiar with these standards. I can briefly
> describe such a function's progression through the standards with a
> short paragraph, if that would help. Using the function fchdir(2) as an
> example, let me know how this sounds:
> 
> HISTORY
>        fchdir()
>               SUSv1, POSIX.1-2001.

I'd make this

		SUSv1, POSIX.1-2001 XSI, POSIX.1-2008.

> 
>    SUSv1
>        fchdir(2)  was first introduced in SUSv1.  The function was then
>        included in POSIX.1-2001, but as an XSI extension.   Finally  in
>        POSIX.1-2008, it was moved to the base specification.

I tend to dislike paragraphs.  This would be interesting for the commit
message.  As you say, all of these names are documented in standards(7),
and I think the above should be readable once you know standards(7).

> 
> By the way, I too find these documents confusing as hell! I only have a
> grasp of them because I happened study them due to a recent
> hyperfixation on portable standards (my autism be like). So I certainly
> get where you're coming from here. I just don't know how much more I can
> describe in the added paragraph before intruding on the job of the
> standards(7) man page.

Agree!  It took me some years to know the standards' history (and
I still have some gaps in the older ones).  :)


Have a lovely day!
Alex

-- 
<https://www.alejandro-colomar.es>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2025-12-23 12:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-20 16:17 Early POSIX versions seldom included in history sections Seth McDonald
2025-12-20 17:44 ` Alejandro Colomar
2025-12-21  8:17   ` Seth McDonald
2025-12-21 12:49     ` Alejandro Colomar
2025-12-22  0:58       ` Collin Funk
2025-12-23  3:56         ` Seth McDonald
2025-12-23 12:43           ` Alejandro Colomar [this message]

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=aUqNNsf3ygIj0mxI@devuan \
    --to=alx@kernel.org \
    --cc=collin.funk1@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=sethmcmail@pm.me \
    /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.