The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Subject: [TUHS] Happy birthday, Internet!
Date: Mon,  9 Apr 2018 11:37:43 -0400 (EDT)	[thread overview]
Message-ID: <20180409153743.D925418C073@mercury.lcs.mit.edu> (raw)

    > From: Clem Cole

    > first of Jan 83 was the day the Arpanet was supposed to be turned off

Err, NCP, not the ARPANet. The latter kept running for quite some time,
serving as the Internet's wide-area backbone, and was only slowly turned off
(IMP by IMP) in the late 80's, with the very last remnants finally being
turned off in 1990.

    > The truth is, it did not happen, there were a few exceptions granted for
    > some sites that were not quite ready (I've forgotten now).

A few, yes, but NCP was indeed turned off for most hosts on January 1, 1983.


    > From: "Erik E. Fair"

    > as of the advent of TCP/IP, all those Ethernet and Chaosnet connected
    > workstations became first class hosts on the Internet, which they
    > could not be before.

Huh? As I just pointed out, TCP/IP (and the Internet) was a going concern well
_before_ January 1, 1983 - and one can confidently say that even had NCP _not_
been turned off, history would have proceeded much as it actually did, since
all the machines not on the ARPANET would have wanted to be connected to the
Internet.

(Also, to be technical, I'm not sure if TCP/IP ever really ran on CHAOSNet
hardware - I know I did a spec for it, and the C Gateway implemented it, and
there was a Unix machine at EECS that tried to use it, but it was not a great
success. Workstations connected to the CHAOSNet as of that date - AFAIK, just
LISP Machines - could only get access to the Internet via service gateways,
since at that point they all only implemented the CHAOS protocols; Symbolics
did TCP/IP somewhat later, IIRC, although I don't know the exact date.)

	Noel


             reply	other threads:[~2018-04-09 15:37 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-09 15:37 Noel Chiappa [this message]
2018-04-10 18:32 ` Clem Cole
2018-04-10 19:11 ` Clem Cole
  -- strict thread matches above, loose matches on Subject: below --
2018-04-09 14:57 Noel Chiappa
2018-04-09 14:52 Noel Chiappa
2018-04-09 15:01 ` Erik E. Fair
2018-04-07 12:50 Noel Chiappa
2018-04-07 14:34 ` Steve Nickolas
2018-04-07 14:44   ` Clem Cole
2018-04-08 23:34   ` Dave Horsfall
2018-04-09  0:06     ` Clem Cole
2018-04-09  1:16       ` Kurt H Maier
2018-04-08 23:34 ` Dave Horsfall
2018-04-07  4:54 Rudi Blom
2018-04-07 15:21 ` Clem Cole
2018-04-06 20:56 Dave Horsfall
2018-04-06 23:10 ` Nemo
2018-04-06 23:19   ` Dave Horsfall
2018-04-06 23:56   ` Kurt H Maier
2017-04-07  4:48 Dave Horsfall
2017-04-07  4:58 ` Warren Toomey
2017-04-07  5:13 ` Lars Brinkhoff
2017-04-07  6:57   ` Greg 'groggy' Lehey
2017-04-08  5:13     ` Dave Horsfall
2017-04-09  0:09       ` Greg 'groggy' Lehey
2017-04-09  2:42       ` Jason Stevens
2017-04-10  5:54   ` Dave Horsfall
2017-04-07 13:55 ` Nemo

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=20180409153743.D925418C073@mercury.lcs.mit.edu \
    --to=jnc@mercury.lcs.mit.edu \
    /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).