From: arnold@skeeve.com
To: tuhs@tuhs.org, pnr@planet.nl
Cc: segaloco@protonmail.com
Subject: [TUHS] Re: Documents for UNIX Collections
Date: Fri, 12 Aug 2022 05:15:52 -0600 [thread overview]
Message-ID: <202208121115.27CBFq0A028975@freefriends.org> (raw)
In-Reply-To: <94434410-26C2-48D5-AC8F-260DC3D3AA4B@planet.nl>
Paul Ruizendaal via TUHS <tuhs@tuhs.org> wrote:
> I’m interested in the journey of SysV IPC. So far I have established
> that these originated in CBUnix, with a lot of thinking on how to optimize
> these around the time that Unix 3.0/4.0/5.0 happened. They did not appear
> in Unix 3.0 / SysIII, and from the Unix 4.0 documentation I gather that
> it was not included there either.
I am not sure you can make that conclusion, as the 4.0 printed documents
did not include the programmer's manual; instead they gave out the
3.0 manual and there was a list of changes somewhere in the other doc.
Unfortunately, without actual 4.0 sources, it will always be a question.
I have this VERY vague memory that I saw IPC in 4.0, but I could
very easily be wrong... It was over 40 years ago, after all. :-)
Arnold
next prev parent reply other threads:[~2022-08-12 11:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 11:01 Paul Ruizendaal via TUHS
2022-08-12 11:15 ` arnold [this message]
2022-08-12 11:41 ` Jonathan Gray
2022-08-12 16:06 ` Warner Losh
2022-08-12 16:37 ` Warner Losh
2022-08-13 19:51 ` Paul Ruizendaal via TUHS
-- strict thread matches above, loose matches on Subject: below --
2022-08-12 1:33 segaloco via TUHS
2022-08-12 2:06 ` G. Branden Robinson
2022-08-12 6:41 ` arnold
2022-08-08 23:52 segaloco via TUHS
2022-08-09 0:37 ` Al Kossow
2022-08-09 7:00 ` segaloco via TUHS
2022-08-09 12:49 ` Al Kossow
2022-08-09 15:14 ` segaloco via TUHS
2022-08-09 17:16 ` Warner Losh
2022-08-09 17:22 ` Will Senn
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=202208121115.27CBFq0A028975@freefriends.org \
--to=arnold@skeeve.com \
--cc=pnr@planet.nl \
--cc=segaloco@protonmail.com \
--cc=tuhs@tuhs.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;
as well as URLs for NNTP newsgroup(s).