The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: Paul Ruizendaal <pnr@planet.nl>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Who designed SysV IPC?
Date: Sat, 24 Jul 2021 15:41:40 -0400	[thread overview]
Message-ID: <CAC20D2OpraFXB_1aE+9vtZyreEtgFx=86VmnaHJe6ODV06zM9A@mail.gmail.com> (raw)
In-Reply-To: <6F5C0B9D-C7EF-4DED-AAA5-241F55A916E6@planet.nl>

[-- Attachment #1: Type: text/plain, Size: 1238 bytes --]

Yeah - they are different, but I'm pretty sure that Dale's work in CB UNIX
came first.   I know I saw the CB/UNIX code as hacks to PWB 1.0 I think
(maybe 2.0) when I was still at CMU in 1978 (Phil Karn had it IIRC).   I
was under the impression that folks at Summit (e.g. UNIX Support Group) had
the job of collecting different features that had been done and putting
them into the AT&T 'Standard' for the operating companies.  I agree it
would be interesting to learn who did the work.  But as I always understood
it, Dale's team gave the CB/UNIX stuff to the USG folks who reimplemented
it, I thought because USG was redoing the memory code and wanted something
that would integrate better.   I suspect it is also possible, Dale and his
team redid it in the key of System V at some point and pushed it back.

Clem
ᐧ

On Sat, Jul 24, 2021 at 2:38 PM Paul Ruizendaal via TUHS <
tuhs@minnie.tuhs.org> wrote:

> Currently reading through IPC in CB Unix 3.0, Vr1-vax and SVr1-pdp11.
>
> The IPC primitives in CB Unix (maus, event and msg) are quite different
> from those in SVr1 (although maus survives in SVr1-pdp11).
>
> It made me wonder: is it still known who designed the IPC primitives for
> SysV?
>
>
>

[-- Attachment #2: Type: text/html, Size: 2082 bytes --]

      reply	other threads:[~2021-07-24 19:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-24 18:36 Paul Ruizendaal via TUHS
2021-07-24 19:41 ` Clem Cole [this message]

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='CAC20D2OpraFXB_1aE+9vtZyreEtgFx=86VmnaHJe6ODV06zM9A@mail.gmail.com' \
    --to=clemc@ccc.com \
    --cc=pnr@planet.nl \
    --cc=tuhs@minnie.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).