From: Clem Cole <email@example.com>
To: Bakul Shah <firstname.lastname@example.org>
Cc: steve jenkin <email@example.com>, TUHS <firstname.lastname@example.org>,
Marc Donner <email@example.com>
Subject: [TUHS] Re: Thoughts on Licenses
Date: Sun, 3 Jul 2022 15:48:33 -0400 [thread overview]
Message-ID: <CAC20D2PoEnCKEb=masdGywXAhsFMoHzHUheqXkPv9SHGdCJ=6A@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1572 bytes --]
On Sun, Jul 3, 2022 at 1:48 PM Bakul Shah <firstname.lastname@example.org> wrote:
> Er.. a "microkernel" without an MMU is basically nothing more than a
> thread switcher (not unlike a variety of "realtime" embedded kernels like
> threadX and what not).
Argue with Andy and not me and read his book. Andy calls it a
message-based uK. Given how they structured it. I would agree.
> I think Tanenbaum's point was that MINIX3 is *nothing* like MINIX1 except
> in name.
Having talked to Andy about this in person, as well as looking at the code,
I think I differ with your interpretation
yes, M3 supports a ton of things M1 did not. But the core API and KPI are
I also know a bit about what Intel uses for the IPMI support as part of my
$ day job. Let's just say this is a great deal that is known outside of
Intel and a good bit that is not and/or misunderstood.
My point that started this rat hole was that Larry made a comment about V7
having little value. I know for a fact Larry's observation was not true.
And how we use the core Minix subsystem (*as a basic V7 platform for a
single custom application* that allows us to manage the server - as I said
to Larry think the LS1-11 on the Vax and the 11/40 on the KL processors)
and offered it as a counter-example. It could have been almost anything
that you called a thread switcher. A simple V7 was 'good enough' and Minux
supplied that for the team.
In fact, I can think of other applications where V6 or V7 is more than
enough for a lot of the tasks.
[-- Attachment #2: Type: text/html, Size: 4280 bytes --]
next prev parent reply other threads:[~2022-07-03 19:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-02 18:15 [TUHS] " Clem Cole
2022-07-02 19:07 ` [TUHS] " Marc Donner
2022-07-02 20:57 ` Warner Losh
2022-07-02 21:02 ` Larry McVoy
2022-07-02 23:54 ` Clem Cole
2022-07-03 2:03 ` Warner Losh
2022-07-03 2:27 ` Larry McVoy
2022-07-03 8:11 ` steve jenkin
[not found] ` <F579710B-5568-431D-92CC-88D49C3D9BE6@gmail.com>
2022-07-03 14:39 ` Larry McVoy
2022-07-03 14:59 ` Clem Cole
2022-07-03 15:30 ` Bakul Shah
2022-07-03 16:26 ` Clem Cole
2022-07-03 16:55 ` Kevin Bowling
2022-07-03 17:15 ` Clem Cole
2022-07-03 17:48 ` Bakul Shah
2022-07-03 19:48 ` Clem Cole [this message]
2022-07-03 21:23 ` Matthias Bruestle
2022-07-03 22:40 ` Clem Cole
2022-07-04 3:01 ` Norman Wilson
2022-07-04 12:33 ` Paul Winalski
2022-07-03 21:38 ` Jay Logue via TUHS
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).