The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Kevin Bowling <kevin.bowling@kev009.com>
To: Rob Pike <robpike@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Bell Labs data center in 1969/70
Date: Thu, 14 Mar 2019 21:03:34 -0700	[thread overview]
Message-ID: <CAK7dMtBM-X4yP8_GWsp9qWa7og-dO0VRaci-_JL57Dxso9-PMQ@mail.gmail.com> (raw)
In-Reply-To: <CAKzdPgyTrz8u+mZFi8d_dOhrrfDcwWmQ2asd7tgXsyTJ3KCW=Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 528 bytes --]

I was amused last weekend after using that Bell Labs product to treat an
old AT&T Long Lines L-Carrier bunker.

Regards,
Kevin

On Thu, Mar 14, 2019 at 1:11 AM Rob Pike <robpike@gmail.com> wrote:

> Maybe it was the bizarro Bell Labs whose existence meant we couldn't have
> the domain belllabs.com.
>
> -rob
>
>
> On Thu, Mar 14, 2019 at 12:26 AM Doug McIlroy <doug@cs.dartmouth.edu>
> wrote:
>
>> Strangely I have no recollection of a Bell Labs branch further
>> west than Denver. What did they do in Oakland?
>>
>> Doug
>>
>

[-- Attachment #2: Type: text/html, Size: 1336 bytes --]

  reply	other threads:[~2019-03-15  4:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-13 13:25 Doug McIlroy
2019-03-14  8:10 ` Rob Pike
2019-03-15  4:03   ` Kevin Bowling [this message]
2019-03-16 21:30   ` Steve Johnson
2019-03-17 18:52     ` Ralph Corderoy
2019-03-17 19:39       ` Arthur Krewat
2019-03-18 15:04         ` John P. Linderman
  -- strict thread matches above, loose matches on Subject: below --
2019-03-12 16:02 Dan Cross
2019-03-12 17:14 ` Clem Cole
2019-03-12 17:17   ` Jon Steinhart
2019-03-12 17:29     ` Clem Cole
2019-03-12 17:31       ` Jon Steinhart
2019-03-12 17:42   ` Paul Winalski
2019-03-13  0:17   ` Greg 'groggy' Lehey
2019-03-13  1:37   ` Dave Horsfall
2019-03-13  8:41     ` Peter Jeremy
2019-03-14 22:12       ` Al Kossow

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=CAK7dMtBM-X4yP8_GWsp9qWa7og-dO0VRaci-_JL57Dxso9-PMQ@mail.gmail.com \
    --to=kevin.bowling@kev009.com \
    --cc=robpike@gmail.com \
    --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).