From: rochkind@basepath.com (Marc Rochkind)
Subject: [TUHS] shared memory on Unix
Date: Wed, 1 Feb 2017 11:07:12 -0700 [thread overview]
Message-ID: <CAOkr1zVE+uz7xC6AyzyVdV6Uif-id4asET34gDXSmDwygejAXQ@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2PJY7yAGARJFsQCOsqiZXKbW-158=kDgHS1V1PHt5YYGw@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2189 bytes --]
OK, just remembered. That acronym for the Columbus shared memory was MAUS,
pronounced "mouse". Multi Access User Space.
--Marc
On Wed, Feb 1, 2017 at 11:01 AM, Clem Cole <clemc at ccc.com> wrote:
>
> On Wed, Feb 1, 2017 at 12:24 PM, Joerg Schilling <schily at schily.net>
> wrote:
>
>> Wasn't shmget() and friends added vor SysV past 1982?
>
>
> AT&T Unix naming get's weird as they hire marketing people that don't
> quite get it.
>
> V6 -> PWB [1.0 ~77] ---|
> | |
> + UNIX/TS[~79] -- + PWB 2.0 [~79] ----- PWB 3.0[~80] <--
> internal name of release
>
>
> The "UNIX Support Group" - aka Summit - is supposed to be creating UNIX
> flavors for the different labs and operating companies and Research is to
> go back to doing research. Thus PWB 3.0 is supposed to start to be a
> "superset" of the features added by the different labs, Columbus, IH,
> *etc*... But it took a few spins before all the different hacks,
> additions were agreed too and added. There was much fighting inside of
> BTL as we see outside.
>
> IIRC an unreleased version of PWB 4.0 had the Columbus features in it as
> Horton points out.
>
> Note that AT&T Marketing renames PWB 3.0 -- System III thinking that
> "Programmer's Workbench" would be a bad name to sell against IBM, and this
> it the first non-research system for License outside of the the labs. If
> you look at the documentation set, et al - it all says PWB 3.0 on the cover
> and throughout Also, the BSD vs AT&T wars basically start around this
> time....
>
> Roll the clock forward and here is an new problem the PWB 4.0 moniker was
> used internally, but AT&T marketing want to get rid of the PWB term - so
> the decree comes down the next release is to be called System V.
>
> Certainly by this point, the Columbus changes had been folded into the
> main line kernel in Summit by then. But as I said, my memory is what made
> it into SystemV and what was in CB-UNIX were similar but a little different.
>
> Clem
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170201/25e84346/attachment.html>
next prev parent reply other threads:[~2017-02-01 18:07 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
2017-02-01 18:01 ` Clem Cole
2017-02-01 18:07 ` Marc Rochkind [this message]
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=CAOkr1zVE+uz7xC6AyzyVdV6Uif-id4asET34gDXSmDwygejAXQ@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).