From: Alejandro Colomar <alx@kernel.org>
To: "Seth McDonald" <sethmcmail@pm.me>,
наб <nabijaczleweli@nabijaczleweli.xyz>
Cc: linux-man <linux-man@vger.kernel.org>,
"G. Branden Robinson" <branden@debian.org>
Subject: Re: Chronological order of BSD, SV, and POSIX.1
Date: Sat, 17 Jan 2026 14:16:03 +0100 [thread overview]
Message-ID: <aWuHPHi-08JB8UAS@devuan> (raw)
In-Reply-To: <aWtmabtT1dFTBCI8@McDaDebianPC>
[-- Attachment #1: Type: text/plain, Size: 2415 bytes --]
[CC += наб, Branden]
On Sat, Jan 17, 2026 at 10:37:36AM +0000, Seth McDonald wrote:
> Hi Alex,
Hi Seth, наб,
> 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
That seems to match standards(7).
There are more SV standards than those documented in standards. I think
we should document these in standards(7):
SVID Issue 2 (1986):
<https://bitsavers.org/pdf/att/unix/SVID/System_V_Interface_Definition_Issue_2_Volume_1_1986.pdf>
SVID Issue 3 (1991):
<https://archive.org/details/systemvinterface0001unse>
I wonder how these influenced early POSIX and ANSI C. I know that some
SVID heavily influenced ANSI C, at least regarding allocation functions.
<https://nabijaczleweli.xyz/content/blogn_t/017-malloc0.html>
Also, I suspect SVID eventually was absorbed by POSIX. POSIX.1-2001 is
known as "Issue 6", and it sometimes refers to earlier issues, and I
don't know if some of those issues refer to SVID or early POSIX
versions. It would be good to document that under standards(7) if we
learn it.
> 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 don't know much of this. I've CCed наб, who I suspect will be able
to confirm much of this, and fill the gaps. Also Branden might know
since he's subscribed to the TUHS mailing list. (You may find TUHS
interesting, if you're into old standards. See <https://www.tuhs.org/>.)
наб, would you mind having a look at standards(7) and fill the gaps?
Links to standards would also be very useful! :-)
> (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!)
:)
Have a lovely day!
Alex
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-01-17 13:16 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 [this message]
[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=aWuHPHi-08JB8UAS@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