The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: ken@google.com (Ken Thompson)
Subject: [TUHS] TUHS Digest, Vol 14, Issue 63
Date: Mon, 16 Jan 2017 11:57:08 -0800	[thread overview]
Message-ID: <CAG=a+ri_rS_YEF-NaAenRQOzaz80Uwcw6x4DnYx0=3SFZg_nsQ@mail.gmail.com> (raw)
In-Reply-To: <20170116192112.GR6647@mcvoy.com>

note: this is my partisan recollection.

a network proposal would arise from the
previous BIG network failure. it would have
a name like super-colossal-inter-galactic-hyper-
bolic-better-than-last-time network.
it would have merits that spoke to the failure
of the last attempt. then some marketeers
(all sun-tanned ex-IBM executives, i do
remember one in particular -- roger moody)
would try to get bell to warp the engineering
so that they had an advantage from the
inside on content. after all, money was to
be made on services, not transportation.
this would make the engineering teeter
and after more and more "requirements"
it would eventually fall. and then we start
over with "stupendous" added to the
new project name.

thus, it is my opinion that it was totally
impossible to make a network with
engineers direct by marketeers. there
are several things that should also
be understood. the bell vs ibm rivalry;
the new competition on phones;
the desire to be in services and not
equipment.



On Mon, Jan 16, 2017 at 11:21 AM, Larry McVoy <lm at mcvoy.com> wrote:
> It is pretty stunning that the company that had the largest network
> in the world (the phone system of course) didn't get packet switching
> at all.  I dunno how Bell Labs was allowed to do all that great work
> with management that clueless, that's a minor (major?) miracle right
> there.
>
> On Mon, Jan 16, 2017 at 11:17:09AM -0800, Steve Johnson wrote:
>> This comment reminded me of an internal talk I attended at Bell
>> Labs.?? It had the single most powerful slide I've ever seen in a
>> talk.?? It was a talk about internal networking, and the slide looked
>> like your standard network diagram -- lots of circles with lots of
>> lines connecting them.?? The computation centers were networked.??
>> UUCP was on there, and datakit.
>>
>> But dead in the middle of the slide was a circle that had absolutely
>> no connections with anything.?? Of course, somebody asked about, and
>> was told "Oh.?? That's the networking department..."
>>
>> As I recall, said department ceased to exist about a month later...
>>
>> ----- Original Message -----
>> From: "Larry McVoy" <lm at mcvoy.com>
>>
>> . . .
>>  AT&T seemed pretty clueless about networking.
>> . . .
>>
>
> --
> ---
> Larry McVoy                  lm at mcvoy.com             http://www.mcvoy.com/lm


  reply	other threads:[~2017-01-16 19:57 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
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 [this message]
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='CAG=a+ri_rS_YEF-NaAenRQOzaz80Uwcw6x4DnYx0=3SFZg_nsQ@mail.gmail.com' \
    --to=ken@google.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).