The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: segaloco via TUHS <tuhs@tuhs.org>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Wiki Page on UNIX Standards
Date: Wed, 05 Jun 2024 23:21:35 +0000	[thread overview]
Message-ID: <v_-_W7qBW8AZwRhUfMs7IwakfOMmFSKImOdnv1ZVrsKHOiOBvowvme38AuM3VN4ZCLP3x2Z-gzlqa-L7nMQtznS4D317fZQ_r3wRfFZZrfM=@protonmail.com> (raw)

Good day everyone, I just wanted to share that I've put up a bit of info as well as some book covers concerning UNIX standards that were published from the 80s til now:

https://wiki.tuhs.org/doku.php?id=publications:standards

I did my best to put down a bit of information about the /usr/group, POSIX, SVID, and SUS/Open Group standards, although there's certainly more to each story than what I put down there.  Still, hopefully it serves to lay out a bit of the history of the actual standards produced over time.

I'm kicking myself because one of the things I could've produced a picture of but didn't save at the time is the cover of IEEE 1003.2, a copy of this popped up on eBay some time in the past year and for reasons I can't recall I didn't order it, nor did I save the picture from the auction at the time.  In any case, if anyone has any published standards that are not visually represented in this article, I'm happy to add any photos or scans you can provide to the page.

Also pardon if the bit on spec 1170/SUS may be shorter than the others.  Admittedly even having most of this on the desk in front of me right now, I'm fuzzy on the lines between POSIX, the Single UNIX Specification, the "Open Group Specification", spec 1170, etc. or if these are all names that ultimately just refer to different generations of the same thing.  Part of getting this information put down is hoping someone will be along to correct inaccuracies :)

Anywho, that's all for now.  Feel free to suggest any corrections or additions!

- Matt G.

                 reply	other threads:[~2024-06-05 23:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='v_-_W7qBW8AZwRhUfMs7IwakfOMmFSKImOdnv1ZVrsKHOiOBvowvme38AuM3VN4ZCLP3x2Z-gzlqa-L7nMQtznS4D317fZQ_r3wRfFZZrfM=@protonmail.com' \
    --to=tuhs@tuhs.org \
    --cc=segaloco@protonmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).