From: rochkind@basepath.com (Marc Rochkind)
Subject: [TUHS] TUHS Digest, Vol 14, Issue 63
Date: Mon, 16 Jan 2017 09:22:09 -0700 [thread overview]
Message-ID: <CAOkr1zUOZuC4v+Sy3gYB01L9tSrBv+BmPaT=3nViO7Shmp3tPA@mail.gmail.com> (raw)
In-Reply-To: <201701161600.v0GG00XA080461@tahoe.cs.Dartmouth.EDU>
Thanks for this, Doug.
When I started at Bell Labs, in the Summer of 1970, my organization was
involved in what I think was called the Digital Data System. I recall that
it was synchronous, meaning, I think, that there were clocks that timed
everything on the network.
Where does that fit into your story?
--Marc
On Mon, Jan 16, 2017 at 9:00 AM, Doug McIlroy <doug at cs.dartmouth.edu> wrote:
> > One thing that I'm unclear about is why all this Arpanet work was not
> filtering more into the versions of Unix done at Bell Labs.
>
> The short answer is that Bell Lbs was not on Arpanet. In the early
> 80s the interim CSNET gave us a dial-up window into Arpanet, which
> primarily served as a conduit for email. When real internet connection
> became possible, network code from Berkeley was folded into the
> research kernel. (I am tempted to say "engulfed the research kernel",
> for this was a huge addition.)
>
> The highest levels of AT&T were happy to carry digital data, but
> did not see digital as significant business. Even though digital T1
> was the backbone of long-distance transmission, it was IBM, not
> AT&T, that offered direct digital interfaces to T1 in the 60s.
>
> When Arpanet came along MCI was far more eager to carry its data
> than AT&T was. It was all very well for Sandy Fraser to build
> experimental data networks in the lab, but this was seen as a
> niche market. AT&T devoted more effort to specialized applications
> like hotel PBXs than to digital communication per se.
>
> Doug
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170116/2862c727/attachment.html>
next prev parent reply other threads:[~2017-01-16 16:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1484532001.2693.tuhs@minnie.tuhs.org>
2017-01-16 16:00 ` Doug McIlroy
2017-01-16 16:22 ` Marc Rochkind [this message]
2017-01-16 16:44 ` Larry McVoy
2017-01-16 16:52 ` Marc Rochkind
2017-01-16 19:17 ` Steve Johnson
2017-01-16 19:21 ` Larry McVoy
2017-01-16 19:57 ` Ken Thompson
2017-01-16 23:41 ` Tim Bradshaw
2017-01-16 23:45 ` Brantley Coile
2017-01-17 4:07 ` Jason Stevens
2017-01-17 5:22 ` William Corcoran
2017-01-17 11:43 ` Jason Stevens
2017-01-17 14:27 ` Joerg Schilling
2017-01-17 14:21 ` Joerg Schilling
2017-01-16 19:46 Noel Chiappa
2017-01-17 0:30 ` Brad Spencer
2017-01-17 15:32 Noel Chiappa
2017-01-18 14:29 ` Paul Ruizendaal
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='CAOkr1zUOZuC4v+Sy3gYB01L9tSrBv+BmPaT=3nViO7Shmp3tPA@mail.gmail.com' \
--to=rochkind@basepath.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).