From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] shared memory on Unix
Date: Wed, 1 Feb 2017 13:04:30 -0500 [thread overview]
Message-ID: <CAC20D2P_nBJD5WDSQeEqYA+eWC67HZThouJY8g7Y_fUYTm0kEA@mail.gmail.com> (raw)
In-Reply-To: <CAOkr1zVY_WLOa+r8FbeZ8+N4aVs9YZeqFd6eem-HnrFbiZdSzw@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 649 bytes --]
On Wed, Feb 1, 2017 at 12:39 PM, Marc Rochkind <rochkind at basepath.com>
wrote:
> 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.
>
This is in sync with my memory of the time.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170201/5344832e/attachment.html>
next prev parent reply other threads:[~2017-02-01 18:04 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
2017-02-01 18:04 ` Clem Cole [this message]
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=CAC20D2P_nBJD5WDSQeEqYA+eWC67HZThouJY8g7Y_fUYTm0kEA@mail.gmail.com \
--to=clemc@ccc.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).