From: Lars Brinkhoff <lars@nocrew.org>
To: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] PDP-11/VAX Unix Chaosnet
Date: Mon, 05 Nov 2018 11:11:42 +0000 [thread overview]
Message-ID: <7wtvkv22z5.fsf@junk.nocrew.org> (raw)
In-Reply-To: <20181105100811.B438E18C0CB@mercury.lcs.mit.edu> (Noel Chiappa's message of "Mon, 5 Nov 2018 05:08:11 -0500 (EST)")
Noel Chiappa wrote:
>> 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.
Because the 4.1BSD Chaosnet I have found only supports CH11. And also,
it would be useful for running MINITS and ITS on SIMH.
next prev parent reply other threads:[~2018-11-05 12:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 10:08 Noel Chiappa
2018-11-05 11:11 ` Lars Brinkhoff [this message]
-- 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=7wtvkv22z5.fsf@junk.nocrew.org \
--to=lars@nocrew.org \
--cc=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).