The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Dan Cross <crossd@gmail.com>
To: ron minnich <rminnich@gmail.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] CSRG at berkeley
Date: Wed, 2 Feb 2022 10:16:27 -0500	[thread overview]
Message-ID: <CAEoi9W6nQen0=ecHruGY7M7DAc8DAG2-U99nVMjpyAEcpyxrEw@mail.gmail.com> (raw)
In-Reply-To: <CAP6exY+n07DL8962Fo9D-gLfvG8LEOQMDTwVp2Wu31RXCOssGQ@mail.gmail.com>

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

On Wed, Feb 2, 2022 at 12:31 AM ron minnich <rminnich@gmail.com> wrote:

> I should have asked the other question: when did DARPA funding start?
>

Salus's "25 Years of Unix" book covers this, and I was surprised to find it
available here:
https://wiki.tuhs.org/lib/exe/fetch.php?media=publications:qcu.pdf

Pages 159-160 or so talks about this: it says the DARPA money appeared in
1980?

        - Dan C.

On Tue, Feb 1, 2022, 8:31 PM Erik E. Fair <fair-tuhs@netbsd.org> wrote:
>
>>
>>         Date: Tue, 1 Feb 2022 20:18:11 -0800
>>         From: Jon Forrest <nobozo@gmail.com>
>>         Subject: Re: [TUHS] CSRG at berkeley
>>
>>         Although not directly related to CSRG, there's an interesting
>>         piece of Unix history at Berkeley recounted in
>>
>>         http://ucbvax.berkeley.edu/passing-of-ucbvax.txt
>>
>>         I was there.
>>
>>         Jon
>>
>>
>> As was I.
>>
>>         Erik
>>
>

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

  reply	other threads:[~2022-02-02 15:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-02  3:02 ron minnich
2022-02-02  4:02 ` Clem Cole
2022-02-02  4:18   ` Jon Forrest
2022-02-02  4:30     ` Erik E. Fair
2022-02-02  5:30       ` ron minnich
2022-02-02 15:16         ` Dan Cross [this message]
2022-02-02 15:28         ` Clem Cole
2022-02-02 15:47           ` ron minnich

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='CAEoi9W6nQen0=ecHruGY7M7DAc8DAG2-U99nVMjpyAEcpyxrEw@mail.gmail.com' \
    --to=crossd@gmail.com \
    --cc=rminnich@gmail.com \
    --cc=tuhs@minnie.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).