The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: rochkind@basepath.com (Marc Rochkind)
Subject: [TUHS] shared memory on Unix
Date: Wed, 1 Feb 2017 10:39:23 -0700	[thread overview]
Message-ID: <CAOkr1zVY_WLOa+r8FbeZ8+N4aVs9YZeqFd6eem-HnrFbiZdSzw@mail.gmail.com> (raw)
In-Reply-To: <589219b1.U4yqSQ1D6ZJhjhk0%schily@schily.net>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1971 bytes --]

The so-called Columbus shared memory feature was in their system in the
mid-1970s, along with a few other things such as semaphores and
inter-process messages. I seem to recall the acronym MAUG, but I may have a
letter or two wrong. Something like Multi Access User ____. The much later
System V features had a completely different API.

Hey, Doug, do you remember this? In the early 1970s, there were a couple of
UNIX meetings at Murray Hill, at which various Bell Labs groups presented
on what they were doing with UNIX, and a group, perhaps Columbus, said that
UNIX wasn't capable of doing what they wanted, so they had modified it. You
asked the question, "Why are you using UNIX?"

To my knowledge, having witnessed another decade or so of groups trying to
bend UNIX to their will, it was the last time the question was asked.

--Marc

On Wed, Feb 1, 2017 at 10:24 AM, Joerg Schilling <schily at schily.net> wrote:

> Mary Ann Horton <mah at mhorton.net> wrote:
>
> > I*'m not sure what you mean by CB3, but these features (shared memory,
> > semaphores, IPC) were added to CB-UNIX (Bell Labs, Columbus) precisely
> > because they were needed in real time telco systems and not preset in
> > the versions from New Jersey.  This would have been in the early 1980s.
> > When I got there in 1981 I think CB-UNIX was already well established
> > and had these features.  (These would show up, ironically, in /usr/ucb,
> > which did not stand for Berkeley.)
>
> Wasn't shmget() and friends added vor SysV past 1982?
>
> Jörg
>
> --
>  EMail:joerg at schily.net                  (home) Jörg Schilling D-13353
> Berlin
>        joerg.schilling at fokus.fraunhofer.de (work) Blog:
> http://schily.blogspot.com/
>  URL:  http://cdrecord.org/private/ http://sourceforge.net/
> projects/schilytools/files/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170201/e4191bac/attachment.html>


  reply	other threads:[~2017-02-01 17:39 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-01 14:18 Paul Ruizendaal
2017-02-01 16:21 ` Mary Ann Horton
2017-02-01 17:18   ` Clem Cole
2017-02-01 17:24   ` Joerg Schilling
2017-02-01 17:39     ` Marc Rochkind [this message]
2017-02-01 18:04       ` Clem Cole
2017-02-01 18:01     ` Clem Cole
2017-02-01 18:07       ` Marc Rochkind
2017-02-01 18:15       ` Joerg Schilling
2017-02-01 18:32         ` Marc Rochkind
2017-02-01 18:35           ` Joerg Schilling
2017-02-01 18:33       ` arnold
2017-02-01 19:11         ` Steve Johnson
2017-02-01 19:24           ` Marc Rochkind
2017-02-01 19:30         ` Clem Cole
2017-02-02  0:25           ` Nick Downing
2017-02-01 23:11   ` Paul Ruizendaal
2017-02-02  1:10     ` Clem Cole
2017-02-01 19:44 Noel Chiappa
2017-02-01 19:55 ` ron minnich
2017-02-01 21:40 ` Larry McVoy

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=CAOkr1zVY_WLOa+r8FbeZ8+N4aVs9YZeqFd6eem-HnrFbiZdSzw@mail.gmail.com \
    --to=rochkind@basepath.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).