The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Paul Winalski <paul.winalski@gmail.com>
To: Clem Cole <clemc@ccc.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Pipes and PRISM
Date: Wed, 2 Mar 2022 13:51:21 -0500	[thread overview]
Message-ID: <CABH=_VT330P7TpBv-9Amp6XVJMd0DWXtCWyCBgLpaCy_NwgzPQ@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2NKys0nxV1o01-=YgZztRA8Cq0mNZkeUhBXKdQZD1r5+A@mail.gmail.com>

On 3/1/22, Clem Cole <clemc@ccc.com> wrote:
> Btw look at Mach if you want to understand nt.  The Mach and Nt tasks are
> very lightweight and primitive so you can build much more complex processes
> from them
>
That's correct,  Dave Cutler was very impressed by Mach's microkernel
idea and used it to implement VAXeln, a VAX OS for real-time
applications (VMS had grown too heavyweight to properly support
real-time).  He used the same design for MICA and later NT.

Cutler had a lot of fights with the Windows developers.  They were
used to MS-DOS, where there was a single application running with no
memory protection, so it could do whatever it pleased as long as it
left the system in a usable state when it exited.  Windows did
cooperative multitasking and it was common practice to insert hooks to
intercept system events and procedures.  Cutler told them, no, there
will be no hooks into the NT privileged kernel--use the system service
calls provided by the NT API.  Over time, the NT microkernel and the
layers on top of it have become less distinct, but the original
concept of a microkernel with personality modules on top of it
remains.  That idea came from Mach.

-Paul W.

  reply	other threads:[~2022-03-02 18:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-01 16:56 Paul Winalski
2022-03-01 21:25 ` Richard Salz
2022-03-01 21:38   ` Larry McVoy
2022-03-01 21:49   ` Clem Cole
2022-03-01 22:09     ` Clem Cole
2022-03-02 18:51       ` Paul Winalski [this message]
2022-03-01 23:42     ` silas poulson
2022-03-02  1:18       ` 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='CABH=_VT330P7TpBv-9Amp6XVJMd0DWXtCWyCBgLpaCy_NwgzPQ@mail.gmail.com' \
    --to=paul.winalski@gmail.com \
    --cc=clemc@ccc.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).