From: Seth McDonald <sethmcmail@pm.me>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man <linux-man@vger.kernel.org>
Subject: Chronological order of BSD, SV, and POSIX.1
Date: Sat, 17 Jan 2026 10:37:36 +0000 [thread overview]
Message-ID: <aWtmabtT1dFTBCI8@McDaDebianPC> (raw)
[-- Attachment #1: Type: text/plain, Size: 1062 bytes --]
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.
(I've also taken your recommendation and am trying out mutt(1), starting
with this email. It's certainly a learning curve, but I'm slowly
getting there!)
--
Take care,
Seth McDonald.
<sethmcmail at pm dot me> (on-list)
2336 E8D2 FEB1 5300 692C 62A9 5839 6AD8 9243 D369
<mcdonald_seth at pm dot me> (off-list)
82B9 620E 53D0 A1AE 2D69 6111 C267 B002 0A90 0289
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 322 bytes --]
next reply other threads:[~2026-01-17 10:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-17 10:37 Seth McDonald [this message]
2026-01-17 13:16 ` Chronological order of BSD, SV, and POSIX.1 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
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=aWtmabtT1dFTBCI8@McDaDebianPC \
--to=sethmcmail@pm.me \
--cc=alx@kernel.org \
--cc=linux-man@vger.kernel.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