The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Stuff Received <stuff@riddermarkfarm.ca>
To: tuhs@tuhs.org
Subject: [TUHS] Re: DG UNIX History
Date: Mon, 14 Nov 2022 20:21:19 -0500	[thread overview]
Message-ID: <46715e7b-b0ae-e160-4ac1-7f7c5ea2b467@riddermarkfarm.ca> (raw)
In-Reply-To: <CAC20D2N9pd-9JjwMnU9ChU5LL4z8N3PGw7g5Bh8dsqxAsGsU7g@mail.gmail.com>

On 2022-11-14 17:31, Clem Cole wrote:
> On Mon, Nov 14, 2022 at 5:12 PM Paul Ruizendaal <pnr@planet.nl> wrote:
>
>     Following on from the exchange on TUHS about DG-UX, it would seem
>     to me that the (Unix) unified cache was invented at least three
>     times for Unix:
>
> Not to quibble too much, but s/cache/memory/  I think is a fairer way 
> of saying that.
>
>     - John Reiser at AT&T
>     - At Sun
>     - At DG
>
> - At CMU (Mach)
>
> The interesting thing again, is that while they while all of these 
> implementations seem to have been technologically 'better' - only Mach 
> lived on from the original developers.  And in the case of Mach, by 
> the time it was mainstream (macOS) the original implementation had 
> been replaced a few times - so while the concepts are there, I don't 
> think much of the Original CMU code is left in XNU/Darwin [or for that 
> matter in the OSF flavors -- Tru64 rewrote it but it died and the 
> OSF/RI kernel never went anywhere either].

The CMU copyrights are still there 
(https://github.com/apple-opensource/xnu/tree/master/osfmk/mach). 
Perhaps someone far more knowledgeable than me could spelunk.

>
> As I said, the lesson to TUHS -- as much as I'm a techie and I am 
> interested in the 'proper' way of doing things ... "good enough" is 
> often what rules.

Indeed.

>
> It's too bad none of the good memory implementations made it into 
> >>systems<< that lasted.
>
> Clem
> ᐧ


  parent reply	other threads:[~2022-11-15  1:21 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-14 22:11 Paul Ruizendaal
2022-11-14 22:31 ` Clem Cole
2022-11-14 23:54   ` Warner Losh
2022-11-15  6:03     ` Theodore Ts'o
2022-11-15 15:11       ` Larry McVoy
2022-11-15 15:48         ` Bakul Shah
2022-11-15 17:47       ` Warner Losh
2022-11-15  1:21   ` Stuff Received [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-11-14 11:44 arnold
2022-11-12 15:54 [TUHS] " Clem Cole
2022-11-12 16:09 ` [TUHS] " Larry McVoy
2022-11-12 16:52 ` arnold
2022-11-12 17:05   ` Larry McVoy
2022-11-12 17:09   ` Miod Vallat
2022-11-12 17:12     ` Warner Losh
2022-11-12 17:39     ` arnold
2022-11-12 17:13   ` David Barto
2022-11-12 17:37   ` Brad Spencer
2022-11-12 18:04   ` Clem Cole
2022-11-12 18:36     ` Larry McVoy
2022-11-12 19:36       ` Clem Cole
2022-11-13  1:56         ` Larry McVoy
2022-11-12 19:16 ` Dave Horsfall
2022-11-12 19:31   ` Clem Cole

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=46715e7b-b0ae-e160-4ac1-7f7c5ea2b467@riddermarkfarm.ca \
    --to=stuff@riddermarkfarm.ca \
    --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).