From: <jsteve@superglobalmegacorp.com>
To: Lars Brinkhoff <lars@nocrew.org>
Cc: "tuhs@tuhs.org" <tuhs@tuhs.org>
Subject: Re: [TUHS] Chaosnet for 4.1BSD
Date: Sun, 18 Nov 2018 20:50:30 +0800 [thread overview]
Message-ID: <b060da67-27dd-4072-be9d-1c4dac8f59d1@SG2APC01FT063.eop-APC01.prod.protection.outlook.com> (raw)
In-Reply-To: <7wbm6naf0a.fsf@junk.nocrew.org>
[-- Attachment #1: Type: text/plain, Size: 1222 bytes --]
When everyone was reading iron man, spider man, x-men I was the weirdo reading “What if?”
Sure tcpip scales, but it wasn’t the first, nor the last.. Much like many of these old systems, owning one is far from practical, let alone a functioning one, but emulation is so convenient.
Just as dynamips is another great hero of emulation, bringing all kinds of networking topologies into play.
I guess it's also a break from the x86_64/arm64 boring of the day to day.
Sent from my Windows 10 Nokia Lumia 1520
From: Lars Brinkhoff
Sent: Saturday, November 17, 2018 11:41 PM
To: jsteve@superglobalmegacorp.com
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] Chaosnet for 4.1BSD
jsteve@superglobalmegacorp.com writes:
> Please post updates as you go!!!
Sure, at least it's both historical and Unix.
The CH11 device is for all SIMH Unibus computers, so VAX, PDP-11, and
PDP-10 (KS1). There supposedly were patches for PDP-11 Unix too, but I
haven't seen them so far.
> I'm always interested in obsolete dead ends like this !
Why oh why is there such a high correlation between archaic obsolete
systems and sheer hacking joy? I'm just dying to have MagicSix on
Chaosnet, but it's not to be.
[-- Attachment #2: Type: text/html, Size: 3467 bytes --]
next prev parent reply other threads:[~2018-11-18 12:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-17 13:10 Lars Brinkhoff
2018-11-17 13:41 ` jsteve
2018-11-17 15:40 ` Lars Brinkhoff
2018-11-17 16:41 ` Larry McVoy
2018-11-17 18:21 ` Grant Taylor via TUHS
2018-11-18 12:50 ` jsteve [this message]
2018-11-29 5:51 ` Lars Brinkhoff
2018-11-29 15:35 ` Warner Losh
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=b060da67-27dd-4072-be9d-1c4dac8f59d1@SG2APC01FT063.eop-APC01.prod.protection.outlook.com \
--to=jsteve@superglobalmegacorp.com \
--cc=lars@nocrew.org \
--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).