From: ron minnich <rminnich@gmail.com>
To: "Erik E. Fair" <fair-tuhs@netbsd.org>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] CSRG at berkeley
Date: Tue, 1 Feb 2022 21:30:27 -0800 [thread overview]
Message-ID: <CAP6exY+n07DL8962Fo9D-gLfvG8LEOQMDTwVp2Wu31RXCOssGQ@mail.gmail.com> (raw)
In-Reply-To: <21873.1643776242@cesium.clock.org>
[-- Attachment #1: Type: text/plain, Size: 555 bytes --]
I should have asked the other question: when did DARPA funding start?
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: 1101 bytes --]
next prev parent reply other threads:[~2022-02-02 5:31 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 [this message]
2022-02-02 15:16 ` Dan Cross
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=CAP6exY+n07DL8962Fo9D-gLfvG8LEOQMDTwVp2Wu31RXCOssGQ@mail.gmail.com \
--to=rminnich@gmail.com \
--cc=fair-tuhs@netbsd.org \
--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).