From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
To: tuhs@tuhs.org
Cc: jnc@mercury.lcs.mit.edu
Subject: Re: [TUHS] PDP-11/VAX Unix Chaosnet
Date: Mon, 5 Nov 2018 05:08:11 -0500 (EST) [thread overview]
Message-ID: <20181105100811.B438E18C0CB@mercury.lcs.mit.edu> (raw)
> From: Lars Brinkhoff
> Let's hope it's OK!
Indeed! It will be fun to see that code.
> I suppose I'll have to add a simulation of the Unibus CH11 Chaosnet
> interface to SIMH.
Why? Once 10M Ethernet hardware was available, people switched pretty rapidly
to using that, instead of the CHAOS hardware. (It was available off the shelf,
and the analog hardware was better designed.) That's part of the reason ARP is
multi-protocol.
Some hard-to-run cables (e.g. under the street from Tech Sq to main campus)
stayed CHAOS hardware because it was easier to just keep using what was there,
but most new machines got Ethernet cards.
Noel
next reply other threads:[~2018-11-05 11:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 10:08 Noel Chiappa [this message]
2018-11-05 11:11 ` Lars Brinkhoff
-- strict thread matches above, loose matches on Subject: below --
2018-11-04 13:48 Lars Brinkhoff
2018-11-04 14:59 ` Clem cole
2018-11-05 7:19 ` Lars Brinkhoff
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=20181105100811.B438E18C0CB@mercury.lcs.mit.edu \
--to=jnc@mercury.lcs.mit.edu \
--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).