The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: Douglas McIlroy <douglas.mcilroy@dartmouth.edu>
Cc: TUHS main list <tuhs@tuhs.org>
Subject: [TUHS] Re: Book: "You Are Not Expected to Understand This"
Date: Mon, 14 Nov 2022 10:50:29 -0500	[thread overview]
Message-ID: <CAC20D2N7t4VQLaRGr+i0GQTySGEBfKDw5sK+es0gp+Jme_CB2g@mail.gmail.com> (raw)
In-Reply-To: <CAKH6PiXhVt6v_KSYcQjq=+rOORgd7d6NpftqTL+MYfW1b81y=g@mail.gmail.com>

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

On Mon, Nov 14, 2022 at 9:16 AM Douglas McIlroy <
douglas.mcilroy@dartmouth.edu> wrote:

> "One view of the memory, period." That describes Multics.
>
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]. They had studied
Multics extensively, and that system supposedly had taken a great deal from
it.  I never completely knew what happened other than something went south
and it end up getting canceled.  I later got to know of a number of the
MV10000 folks (who later joined us in the HW team at Stellar).   But I
believe a bit issue with Fountain Head was both new HW and SW, whereas the
MV10000 allowed Nova /Eclipse code to 'just work.'  [Kidder makes a big
deal out of this in the book].

The lessons and relevance to TUHS I think are a couple of things:
1.) When they did DG-UX, the SW folks had previously developed a kernel
with that view, so it's not surprising.
2.) Cost of >>solution development<< is the real end-customer/deployer
driver (economics beats architecture).

Clem
ᐧ

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

  reply	other threads:[~2022-11-14 15:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-14 14:14 Douglas McIlroy
2022-11-14 15:50 ` Clem Cole [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-11-14 16:58 Norman Wilson
2022-11-14 19:17 ` Larry McVoy
2022-11-14 19:50   ` Dave Horsfall
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=CAC20D2N7t4VQLaRGr+i0GQTySGEBfKDw5sK+es0gp+Jme_CB2g@mail.gmail.com \
    --to=clemc@ccc.com \
    --cc=douglas.mcilroy@dartmouth.edu \
    --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).