The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: dscherrer@solar.stanford.edu (Deborah Scherrer)
Subject: [TUHS] ARPAnet now 4 nodes
Date: Mon, 4 Dec 2017 17:13:20 -0800	[thread overview]
Message-ID: <1afac5da-82db-489d-320f-e3eb74f67216@solar.stanford.edu> (raw)
In-Reply-To: <20171205010520.2C91C18C087@mercury.lcs.mit.edu>

LBL was part of UC Berkeley.  We were funded by DOE, who was working 
with DARPA.  But we were UC employees.  LBL had a contract with
DOE/DARPA to evaluate an early version of the the arpanet.  I was just 
getting started at that time, so only slightly involved.  The people I 
remember were Dennis Hall, Joe Sventek, Carl Quong & several other guys 
in EE.  A lot of the TCP/IP development was done at the Lab.

We also worked heavily with the CS people on campus.  I think this was 
before Kirk McKusick, Bill Joy, et al.

Debbie

On 12/4/17 5:05 PM, Noel Chiappa wrote:
>      > From: Deborah Scherrer
>
>      > the initial research on the arpanet was done at Lawrence Berkeley Lab
>
> I was interested to find out more about this: I looked in Hafner, "Where
> Wizards Stay Up Late" (the popular, but well-researched, book on the ARPANET)
> but couldn't find 'Lawrence Berkeley' or 'LBL' in the index (although it did
> have Lawrence Livermore); there were a couple of 'Californa, University of (at
> Berkeley' listings, but none covered this. In Abbate, "Inventing the Internet"
> (the first half of which covers the ARPANET), nothing under any of 'Lawrence
> Berkeley', 'LBL', 'Berkeley' or 'California'.
>
> In Norberg/O'Neill, "Transforming Computer Technology" (the standard ARPA
> history, which has extensive coverage of the ARPANET project), there was one
> entry for 'Californa, University (Berkeley)', which might be about the work
> you refer to:
>
>    "IPTO issued a contract for a 'network' project at the Berkeley campus of
>    the University of California ... because of the presence at Berkeley of
>    specialists in programming languages and heuristic programming".
>
> But there's nothing about what was produced. Is there anything you can point
> me at that provides more detail? Thanks!
>
>     Noel




  reply	other threads:[~2017-12-05  1:13 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-05  1:05 Noel Chiappa
2017-12-05  1:13 ` Deborah Scherrer [this message]
2017-12-05  1:38 ` Jon Forrest
2017-12-05  1:56   ` Deborah Scherrer
  -- strict thread matches above, loose matches on Subject: below --
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
2017-12-05 15:22 Noel Chiappa
     [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
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-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=1afac5da-82db-489d-320f-e3eb74f67216@solar.stanford.edu \
    --to=dscherrer@solar.stanford.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).