From: mike.ab3ap@gmail.com (Mike Markowski)
Subject: [TUHS] Masscomp - Real Time Unix (RTU) an early UNIX based system, the first commercial multiprocessor and was realtime
Date: Thu, 22 Mar 2018 15:02:55 -0400 [thread overview]
Message-ID: <CANq1pfkdxOG6nJ4uibn3+b1D4w-oH7AV4dT_5n-qkihP7KpX1Q@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2MrAJBorJcOUUX3RMmEEU+A+vwEX41z2n=XeNds0DUXYA@mail.gmail.com>
On Thu, Mar 22, 2018 at 1:10 PM, Clem Cole <clemc at ccc.com> wrote:
> On Wed, Mar 21, 2018 at 7:50 PM, Larry McVoy <lm at mcvoy.com> wrote:
>
>> I was sys admin for a Masscomp with a 40MB disk
>
> Right an early MC-500/DP system - although I think the minimum was a 20M
> [ST-506 based] disk.
>
> On Wed, Mar 21, 2018 at 8:55 PM, Mike Markowski <mike.ab3ap at gmail.com>
> wrote:
>
>> I remember Masscomp ... it allowed data acquisition to not be swapped
>>> out.
>>>
>> Actually, not quite right in how it worked, but in practice you got the
> desired behavior. More in a minute.
>
[...lots of good stuff...]
>
> Clem
>
Thanks very much, Clem! I had no idea what was under the hood of the
Masscomps I was using then, fresh out of grad school. I was on a team
designing a tracking radar system and using the Masscomp as a tool to
control gear and acquire the return signals. All my attention was on that
and not so much the computer itself. Super interesting to learn about it.
Mike Markowski
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20180322/5ca17d66/attachment.html>
prev parent reply other threads:[~2018-03-22 19:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-22 17:10 Clem Cole
2018-03-22 19:02 ` Mike Markowski [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=CANq1pfkdxOG6nJ4uibn3+b1D4w-oH7AV4dT_5n-qkihP7KpX1Q@mail.gmail.com \
--to=mike.ab3ap@gmail.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).