The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: pnr@planet.nl (Paul Ruizendaal)
Subject: [TUHS] ARPAnet now 4 nodes
Date: Tue, 5 Dec 2017 09:14:29 +0100	[thread overview]
Message-ID: <3AE304EA-6742-4558-A98A-3E2C1601BE67@planet.nl> (raw)
In-Reply-To: <mailman.395.1512445587.9955.tuhs@minnie.tuhs.org>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1249 bytes --]

I don’t think anybody was thinking you wilfully misrepresented things,
it is always interesting to hear about strands of history that might
have been missed earlier.

It would be helpful to better understand the time period, people
involved and the scope of work.

I’m a bit confused as to what time period you are referring to: I
think you are referring to the initial development of Arpanet, i.e.
the second half of the sixties. Is that correct?

There is a page here with some info on events in that period and it
may have missed some interesting development work done at LBL:
https://www.livinginternet.com/i/ii_roberts.htm

Paul

> 
> Message: 7
> Date: Mon, 4 Dec 2017 19:46:21 -0800
> From: Deborah Scherrer <dscherrer at solar.stanford.edu>
> To: tuhs at minnie.tuhs.org
> Subject: Re: [TUHS] ARPAnet now 4 nodes
> Message-ID: <8254fc85-12e6-4730-8f14-faf060ad6a70 at solar.stanford.edu>
> Content-Type: text/plain; charset=windows-1252; format=flowed
> 
> Yes, Van Jacobson was involved.  Great guy.  So sorry you feel the need 
> to think I am lying.  Why would I make up this stuff?  I was a
> teeny tiny piece of it.  Doesn't affect my career one way or other.   I 
> don't care what you believe, but this really did happen.
> 
> D


       reply	other threads:[~2017-12-05  8:14 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.395.1512445587.9955.tuhs@minnie.tuhs.org>
2017-12-05  8:14 ` Paul Ruizendaal [this message]
2017-12-05  8:24 ` Paul Ruizendaal
2017-12-05 14:46   ` Jon Forrest
2017-12-05 14:52   ` William Cheswick
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
  -- strict thread matches above, loose matches on Subject: below --
2017-12-05 15:22 Noel Chiappa
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-05  1:05 Noel Chiappa
2017-12-05  1:13 ` Deborah Scherrer
2017-12-05  1:38 ` Jon Forrest
2017-12-05  1:56   ` 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=3AE304EA-6742-4558-A98A-3E2C1601BE67@planet.nl \
    --to=pnr@planet.nl \
    /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).