From: Jason Stevens <jsteve@superglobalmegacorp.com>
To: <tuhs@minnie.tuhs.org>, Jon Forrest <nobozo@gmail.com>
Subject: Re: [TUHS] CMU Mach sources?
Date: Sun, 23 Jun 2019 14:03:56 +0000 [thread overview]
Message-ID: <ADFDF14544A65F35.ee15eda2-6576-4f45-b82f-f3c92872db3c@mail.outlook.com> (raw)
In-Reply-To: <8d4e21dd-f2f8-347b-94c3-072898c01c54@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1734 bytes --]
I guess XNU is the 'fixed' version of Mach. At least it powers all those iPhones and iPads.
And I do have the buildable source of Darwin 0.1/0.3 which is the equivalent of OS X Server 1.0
It's a.. Fusion of Mach 2.5 and 4.4BSD. I've heard that NeXTSTEP is more 4.3BSD
Get Outlook for Android
On Sun, Jun 23, 2019 at 9:40 PM +0800, "Jon Forrest" <nobozo@gmail.com> wrote:
On 6/22/2019 10:15 PM, Larry McVoy wrote:
> I've read the Mach source. Not a fan. If you look around you can find
> SunOS 4.x sources, not legal but it is out there.
> If you read the Mach code, nope, it's a tangled mess, there is no
> clear picture there.
>
> I read the papers and wanted to believe it was good, it is not.
There's one thing to keep in mind about some software produced in
an academic environment. Sometimes it's a collection of proofs of
concept of clever ideas that various grad student have hacked together
for their MS or PhD work. It's not intended to be production quality.
I don't know anything about Mach, but this was certainly the state
of Postgres when I worked in the Postgres group in 1991-1995. We
tried to use it as the basis for a big research project (e.g. Sequoia
2000) but spent (wasted?) lots of time fighting Postgres issues.
Eventually, long after I left the group, and after Mike Stonebraker
left Berkeley, a group of people who weren't associated with UC Berkeley
did a truly heroic job and "fixed" Postgres. The production quality
Postgres you see now is the result.
The BSD project was different, for all kinds of reasons.
I wonder if Mach was a Postgres or BSD style project.
Cordially,
Jon Forrest
[-- Attachment #2: Type: text/html, Size: 2737 bytes --]
next prev parent reply other threads:[~2019-06-23 14:05 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 [this message]
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
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=ADFDF14544A65F35.ee15eda2-6576-4f45-b82f-f3c92872db3c@mail.outlook.com \
--to=jsteve@superglobalmegacorp.com \
--cc=nobozo@gmail.com \
--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).