From: ches@cheswick.com (William Cheswick)
Subject: [TUHS] ARPAnet now 4 nodes
Date: Tue, 5 Dec 2017 09:52:17 -0500 [thread overview]
Message-ID: <E52E64F7-99EF-45F4-B919-59A307A2F0DC@cheswick.com> (raw)
In-Reply-To: <5DC50DA3-0165-4139-AA3A-30FCA569C2FD@planet.nl>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 896 bytes --]
I really wonder how the CDC link worked. The channels were electrically strange, and certainly not easily amenable to communicating with anything other than CDC controllers or perhaps a serial line through one of the front ends.
I did hear of a proposal at NADC around 1977 to try to hook into telnet and ftp from a CDC using some hack of the serial stuff. The idea didn’t impress me: it would have taken a lot of hacking to get a kludge working. It always took a lot to make CDC hardware play well with others.
> On 5Dec 2017, at 3:24 AM, Paul Ruizendaal <pnr at planet.nl> wrote:
>
> - In 1974, the Lab’s CDC 6600 became the first online supercomputer when it was connected to ARPANET, the Internet’s predecessor.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20171205/c6f82f13/attachment.html>
next prev parent reply other threads:[~2017-12-05 14:52 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.395.1512445587.9955.tuhs@minnie.tuhs.org>
2017-12-05 8:14 ` Paul Ruizendaal
2017-12-05 8:24 ` Paul Ruizendaal
2017-12-05 14:46 ` Jon Forrest
2017-12-05 14:52 ` William Cheswick [this message]
2018-12-04 20:44 Dave Horsfall
2018-12-04 20:50 ` Clem Cole
2018-12-04 20:57 ` Clem Cole
2018-12-04 20:57 ` Lars Brinkhoff
2018-12-04 22:06 ` Jon Forrest
2018-12-04 22:14 ` Larry McVoy
-- strict thread matches above, loose matches on Subject: below --
2017-12-05 15:22 Noel Chiappa
2017-12-05 3:43 Noel Chiappa
2017-12-05 3:46 ` Deborah Scherrer
2017-12-05 3:49 ` Dan Cross
2017-12-05 2:52 Noel Chiappa
2017-12-05 3:10 ` Deborah Scherrer
2017-12-05 1:05 Noel Chiappa
2017-12-05 1:13 ` Deborah Scherrer
2017-12-05 1:38 ` Jon Forrest
2017-12-05 1:56 ` Deborah Scherrer
2017-12-04 23:44 Noel Chiappa
2017-12-04 23:42 Noel Chiappa
2017-12-04 23:06 Dave Horsfall
2017-12-04 23:14 ` Jon Forrest
2017-12-04 23:18 ` Deborah Scherrer
2017-12-08 2:08 ` Dave Horsfall
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=E52E64F7-99EF-45F4-B919-59A307A2F0DC@cheswick.com \
--to=ches@cheswick.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).