From: Warner Losh <imp@bsdimp.com>
To: Jonathan Gray <jsg@jsg.id.au>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>,
Paul Ruizendaal <pnr@planet.nl>,
segaloco <segaloco@protonmail.com>
Subject: [TUHS] Re: Documents for UNIX Collections
Date: Fri, 12 Aug 2022 10:37:32 -0600 [thread overview]
Message-ID: <CANCZdfqsTQVwR4gJ3xqXH6EZ-K9gtfbAX9E_siku-KnXn5cRDA@mail.gmail.com> (raw)
In-Reply-To: <CANCZdfpXq1nUkSupUZe1MpdbkJ0GW8Did_U6k5xpiCy4VLVTig@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3269 bytes --]
On Fri, Aug 12, 2022 at 10:06 AM Warner Losh <imp@bsdimp.com> wrote:
>
>
> On Fri, Aug 12, 2022 at 5:42 AM Jonathan Gray <jsg@jsg.id.au> wrote:
>
>> On Fri, Aug 12, 2022 at 05:15:52AM -0600, arnold@skeeve.com wrote:
>> > 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. :-)
>>
>> "Release 4.0 was launched from this organization in March. It introduced
>> new IPC mechanisms"
>>
>> from pg 39 of Pirzada's thesis
>>
>> https://spiral.imperial.ac.uk/bitstream/10044/1/7942/1/Shamim_Sharfuddin_Pirzada-1988-PhD-Thesis.pdf
>
>
> But also "Release 4.2 was launched in February 1982 for both the 3B & the
> DEC
> machines. It contained improvements to the data communications and
> networking
> software and more mature IPC" though it goes on to say 4.2 was
> provisional. 5.0
> did have more things from CBUNIX: init and getty.
>
> I've also found this:
>
> https://groups.google.com/g/net.unix/c/-H9x36DMOBQ/m/P_G_s9SJBrgJ
>
> "Eventually, UNIX/TS was augmented to have
> many of the features present in CB-UNIX (this was done by Roger Faulkner
> at Indian Hill, BTL. This, in turn, became the base for UNIX 4.0, which
> was never released externally."
>
> This from a supervisor at Columbus...
>
Oh, see also the message from Guy Harris a few messages previous to the one
that opens up with the above link (minor edits by me):
"
doug_gwyn>The UNIX System V IPC was already present in USG UNIX 4.1.
doug_gwyn>(Not related to 4.1BSD.)
For you real UNIX trivia freaks, the USG 4.0 IPC was different
from the USG 4.1 IPC. The original message send/receive system calls sent
to a process ID; they were changed to send to message queues, which had a
32-bit unique ID, instead (which makes more sense, as it permits you to
transparently replace servers).
"
The note is extensive and goes into a lot of other areas related to IPC and
lists names
and references too. In fact the whole thread is a good candidate to be
hoisted from
google groups while we have the chance and placed into the TUHS archive. Is
there
a process for that?
Warner
Warner
>
> referred to in tuhs/Documentation/Emails/dmr_wkt
>>
>> "Other treasures: Shamim Pirzada did most of a PhD thesis on Unix
>> as an exemplar of software evolution for Imperial College (London)
>> that (in the part I have) contains a pretty good account of details
>> of history up to about 1988."
>>
>
[-- Attachment #2: Type: text/html, Size: 5993 bytes --]
next prev parent reply other threads:[~2022-08-12 16:38 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
2022-08-12 11:41 ` Jonathan Gray
2022-08-12 16:06 ` Warner Losh
2022-08-12 16:37 ` Warner Losh [this message]
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=CANCZdfqsTQVwR4gJ3xqXH6EZ-K9gtfbAX9E_siku-KnXn5cRDA@mail.gmail.com \
--to=imp@bsdimp.com \
--cc=jsg@jsg.id.au \
--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).