From: Chris Hanson <cmhanson@eschatologist.net>
To: Tuhs <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] CMU Mach sources?
Date: Wed, 26 Jun 2019 18:26:50 -0700 [thread overview]
Message-ID: <E8FC8256-BB0A-4FBF-8F74-83E9455BB7B2@eschatologist.net> (raw)
In-Reply-To: <20190627010224.GC1206@mcvoy.com>
On Jun 26, 2019, at 6:02 PM, Larry McVoy <lm@mcvoy.com> wrote:
> Anyone who has read the code would have a hard time reconciling their
> code with the picture they painted in their papers. And indeed, the
> Mach supporters have said nothing about the code, other than to say it
> is a research system and you can't expect clean code.
Then I’ll say it: I did find the Mach code plenty clean *for what it was trying to accomplish* — providing the layering and abstractions necessary to make extensible what had traditionally been kernel code, including allowing it to be developed out-of-tree.
-- Chris
next prev parent reply other threads:[~2019-06-27 1:27 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-23 4:38 Chris Hanson
2019-06-23 5:15 ` Larry McVoy
2019-06-23 8:52 ` Andrew Warkentin
2019-06-23 13:39 ` Jon Forrest
2019-06-23 13:59 ` arnold
2019-06-23 14:03 ` Jason Stevens
2019-06-23 8:04 ` Jason Stevens
2019-06-23 14:54 ` Henry Bent
2019-06-23 21:52 ` Clem Cole
2019-06-25 0:06 ` Larry McVoy
2019-06-25 0:31 ` Theodore Ts'o
2019-06-25 0:45 ` Larry McVoy
2019-06-25 0:55 ` Kurt H Maier
2019-06-25 4:18 ` Larry McVoy
2019-06-26 23:19 ` [TUHS] Craft vs Research (Re: " Bakul Shah
2019-06-27 0:16 ` tuhs
2019-06-27 17:06 ` Clem Cole
2019-06-25 1:00 ` [TUHS] " Richard Salz
2019-06-25 8:00 ` Kevin Bowling
2019-06-25 12:11 ` Arthur Krewat
2019-06-25 12:17 ` Arthur Krewat
2019-06-26 2:45 ` Kurt H Maier
2019-06-26 2:56 ` Larry McVoy
2019-06-26 15:11 ` Theodore Ts'o
2019-06-26 17:44 ` Larry McVoy
2019-06-26 18:01 ` arnold
2019-06-26 18:18 ` Warner Losh
2019-06-26 19:22 ` Chris Hanson
2019-06-26 19:32 ` Ben Greenfield via TUHS
2019-06-26 20:21 ` Larry McVoy
2019-06-27 0:22 ` Chris Hanson
2019-06-27 1:02 ` Larry McVoy
2019-06-27 1:26 ` Chris Hanson [this message]
2019-06-27 4:01 ` Lyndon Nerenberg
2019-06-27 10:34 ` Ben Greenfield via TUHS
2019-06-27 10:59 ` arnold
2019-06-27 11:13 ` Ben Greenfield via TUHS
2019-06-27 11:39 ` arnold
2019-06-27 14:58 ` Warner Losh
2019-06-27 17:25 ` Larry McVoy
2019-06-26 19:30 ` Dennis Boone
2019-06-26 19:25 ` Adam Thornton
2019-06-23 8:27 ` Kevin Bowling
2019-06-25 3:07 ` Gregg Levine
2019-06-25 8:15 ` Kevin Bowling
2019-06-25 18:18 ` Chris Hanson
2019-06-25 20:23 ` Gregg Levine
2019-06-26 1:04 ` Jason Stevens
2019-06-26 0:53 ` Jason Stevens
2019-06-25 7:49 ` Jason Stevens
2019-06-25 7:59 ` Andreas Grapentin
2019-06-23 22:08 Noel Chiappa
2019-06-23 23:54 ` Theodore Ts'o
2019-06-24 17:04 ` Jason Stevens
2019-07-01 13:20 Jason Stevens
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=E8FC8256-BB0A-4FBF-8F74-83E9455BB7B2@eschatologist.net \
--to=cmhanson@eschatologist.net \
--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).