From: Alejandro Colomar <alx@kernel.org>
To: Seth McDonald <sethmcmail@pm.me>
Cc: linux-man <linux-man@vger.kernel.org>,
наб <nabijaczleweli@nabijaczleweli.xyz>,
"G. Branden Robinson" <branden@debian.org>
Subject: Re: Chronological order of BSD, SV, and POSIX.1
Date: Sun, 18 Jan 2026 15:08:33 +0100 [thread overview]
Message-ID: <aWzk8dtIvNSdVlkY@devuan> (raw)
In-Reply-To: <aWtmabtT1dFTBCI8@McDaDebianPC>
[-- Attachment #1: Type: text/plain, Size: 1703 bytes --]
Hi Seth,
On Sat, Jan 17, 2026 at 10:37:36AM +0000, Seth McDonald wrote:
> Hi Alex,
>
> In my next patch set (for system calls), I've generally been ordering
> POSIX.1-1988/1990 relative to BSD and SV according to their release
> years as specified in standards(7). Which gives the following relative
> ordering between SV and POSIX.1:
>
> SVr1
> SVr2
> SVr3
> POSIX.1-1988
> SVr4
> POSIX.1-1990
> SVID 4
>
> And the following relative ordering between BSD and POSIX.1:
>
> 3BSD
> 4BSD
> 4.1BSD
> 4.2BSD
> 4.3BSD
> POSIX.1-1988
> POSIX.1-1990
> 4.4BSD
>
> Because many of the system calls I updated listed SVr4, and some listed
> 4.4BSD, I want to check that it makes sense to list them after
> POSIX.1-1988. In case, for example, SVr4 is known to have influenced
> POSIX.1-1988 prior to being officially released.
Going back to this, yes, 4.4BSD seems clearly later than POSIX.1-1990.
SVr4 seems contemporaneous to POSIX.1-1988, so I don't mind whether we
put it before or after. I think I'd put it before, because as you say,
it heavily influenced, even though formally POSIX.1-1988 seems to
derive from SVr3 (SVID Issue 2). That also puts all SysV before all
POSIX, which seems cleaner.
Let's try to specify the order in the format you used above:
3BSD
4BSD
4.1BSD
SysIII
Unix/TS 4
4.2BSD
SVr1
SVr2
4.3BSD
SVr3
SVr4
C89
POSIX.1-1988
XPG3
POSIX.1-1990
XPG4
SUSv1
SVID 4
4.4BSD
C95
POSIX.1-1996
SUSv2
C99
POSIX.1-2001 SUSv3
POSIX.1-2008 SUSv4
C11
C17
POSIX.1-2024 SUSv5
C23
Have a lovely day!
Alex
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2026-01-18 14:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-17 10:37 Chronological order of BSD, SV, and POSIX.1 Seth McDonald
2026-01-17 13:16 ` Alejandro Colomar
[not found] ` <4dhcmq7vwbkiw5ik4nivsdli2pfb7d3xchchshgyz7cejw7sqk@tarta.nabijaczleweli.xyz>
[not found] ` <aWvBujsIFzewikif@devuan>
[not found] ` <fiwqsh3cg5js2iuouv62zep53ikwkokrb4exiwr4yufze3d7uj@tarta.nabijaczleweli.xyz>
2026-01-18 1:51 ` Alejandro Colomar
2026-01-18 2:33 ` G. Branden Robinson
2026-01-18 13:48 ` Alejandro Colomar
2026-01-18 14:08 ` 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=aWzk8dtIvNSdVlkY@devuan \
--to=alx@kernel.org \
--cc=branden@debian.org \
--cc=linux-man@vger.kernel.org \
--cc=nabijaczleweli@nabijaczleweli.xyz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox