From: Clem Cole <clemc@ccc.com>
To: Paul Winalski <paul.winalski@gmail.com>
Cc: Paul Ruizendaal <pnr@planet.nl>,
The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Early multiprocessor Unix
Date: Mon, 28 Nov 2022 11:49:57 -0500 [thread overview]
Message-ID: <CAC20D2Ot+VAna7cH2M5_Wb=J5n7PpBt+BN=dAGQfs7DGid99xg@mail.gmail.com> (raw)
In-Reply-To: <CABH=_VQhoRTzHyB7pMzA2OfdbLTSPZq2fO2R4DJJcpzD-RUDgw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 369 bytes --]
On Mon, Nov 28, 2022 at 11:30 AM Paul Winalski <paul.winalski@gmail.com>
wrote:
> > configuration. He spliced a second 780 CPU onto the SMB
>
> SBI (Synchronous Backplane Interconnect),
>
right SBI -- thanks, Paul -- too many TLAs - bad cache refill.
>
> I don't know if Ultrix ever supported the 11/782.
>
no - the Ultrix group never bothered.
ᐧ
[-- Attachment #2: Type: text/html, Size: 1569 bytes --]
next prev parent reply other threads:[~2022-11-28 16:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 13:24 [TUHS] " Paul Ruizendaal
2022-11-28 13:42 ` [TUHS] " Larry Stewart
2022-11-28 14:05 ` Clem Cole
2022-11-28 14:13 ` Clem Cole
2022-11-28 14:19 ` Warner Losh
2023-08-06 14:19 ` Warner Losh
2022-11-28 14:16 ` Warner Losh
2022-11-28 14:50 ` Clem Cole
2022-11-28 16:30 ` Paul Winalski
2022-11-28 16:49 ` Clem Cole [this message]
2023-08-06 14:12 ` Warner Losh
2022-11-28 16:52 ` Jonathan Gray
2022-11-29 9:39 ` Jonathan Gray
2022-11-29 15:54 ` [TUHS] First supercomputer UNIX: The Denelcor HEP (was Early multiprocessor Unix) Ron Natalie
2022-11-29 17:00 ` [TUHS] " Jon Steinhart
2022-11-29 20:53 ` steve jenkin
2023-08-05 23:00 ` [TUHS] Re: Early multiprocessor Unix scj
2023-08-06 0:54 ` Larry McVoy
2023-08-06 6:52 ` Paul Ruizendaal
2023-08-06 9:28 ` Ronald Natalie
2023-08-06 9:57 ` Ralph Corderoy
2022-11-30 2:55 Rudi Blom
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='CAC20D2Ot+VAna7cH2M5_Wb=J5n7PpBt+BN=dAGQfs7DGid99xg@mail.gmail.com' \
--to=clemc@ccc.com \
--cc=paul.winalski@gmail.com \
--cc=pnr@planet.nl \
--cc=tuhs@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).