From: norman@oclsc.org (Norman Wilson)
To: tuhs@tuhs.org
Subject: [TUHS] Re: Book: "You Are Not Expected to Understand This"
Date: Mon, 14 Nov 2022 11:58:36 -0500 (EST) [thread overview]
Message-ID: <221091F111EBACF012E50DDA19871666.for-standards-violators@oclsc.org> (raw)
Clem Cole:
Yep -- but not surprising. There were a bunch of folks at DG that had
worked on a single-level store system (Project Fountain-Head) that had
failed [some of that story is described in Kidder's book].
====
Are you sure? I thought Fountainhead was a Rand project.
Norman Wilson
Toronto ON
PS: if you don't get it, consider yourself fortunate.
next reply other threads:[~2022-11-14 16:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 16:58 Norman Wilson [this message]
2022-11-14 19:17 ` Larry McVoy
2022-11-14 19:50 ` Dave Horsfall
-- strict thread matches above, loose matches on Subject: below --
2022-11-14 14:14 Douglas McIlroy
2022-11-14 15:50 ` Clem Cole
2022-11-13 0:02 [TUHS] " Dave Horsfall
2022-11-13 0:25 ` [TUHS] " Kenneth Goodwin
2022-11-13 1:12 ` Rob Pike
2022-11-13 1:52 ` Larry McVoy
2022-11-13 1:12 ` Stuff Received
2022-11-13 21:58 ` Dave Horsfall
2022-11-14 22:48 ` 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=221091F111EBACF012E50DDA19871666.for-standards-violators@oclsc.org \
--to=norman@oclsc.org \
--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).