From: Bakul Shah <email@example.com>
To: Clem Cole <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 12:48:02 -0500 [thread overview]
Message-ID: <08E9845C-CA79-4CBD-B7F1-508F0E5D1AF6@iitbombay.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2524 bytes --]
On Jul 3, 2022, at 11:26 AM, Clem Cole <firstname.lastname@example.org> wrote:
> On Sun, Jul 3, 2022 at 11:30 AM Bakul Shah <email@example.com <mailto:firstname.lastname@example.org>> wrote:
> You may be thinking of MINIX 1. It was a from-scratch implementation that was syscall compatible with V7 but IIRC it didn't have any sort of memory protection as it was designed to run on 8088.
> Minux and specifically M1 was and always has been, a uK. And yes, M1 does not need an MMU - since it was designed to run on an 8088. IIRC this was Linus' original objection when he wanted to run on his 386-based PC (Wyse 32:16 box, IIRC). The key was Andy wanted to teach his students about V7 without running afoul of the AT&T license as Lions had with V6.
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).
> What runs on the Intel Management Engine
> It's called the Intelligent Platform Management Interface <https://streaklinks.com/BHBsBCyMjMy7xGTaiw4nohuO/https%3A%2F%2Fwww.intel.com%2Fcontent%2Fwww%2Fus%2Fen%2Fproducts%2Fdocs%2Fservers%2Fipmi%2Fipmi-second-gen-interface-spec-v2-rev1-1.html> - a.k.a. IPMI
> is MINIX 3, ... with NetBSD userland.
> Actually, if you want to pick nits, neither statement is correct (remember for whom I work).
Not sure which statements you are talking about that are incorrect.
Minix3 running on ME was in the news a few years back. See for instance: https://itsfoss.com/fact-intel-minix-case/ -- Websearch reveals many articles on IME + MINIX, hardly any to IPMI + MINIX.
MINIX 3 + NetBSD userland is pretty much what minix3.org website says!
[And no, I was not aware of who you work for.]
In any case, sounds like you were talking about something not (well)known outside of Intel.
> MINIX 1 and MINIX 3 are related
> That's because M3 added the MMU support that M1 lacked. But there is nothing in M3 that IPMI is using other than it is the current version from Andy's team. What IPMI has as an underlying uK is heavily hacked and is a 'derivative work' - the local uk is basically providing V7 interfaces to some special programs.
I think Tanenbaum's point was that MINIX3 is nothing like MINIX1 except in name.
> It made little sense to recreate something for the platform engine, and Minux was picked because it was smaller than any of the *BSDs and was not GPL'ed so Intel IP was still protected.
No argument here :-)
[-- Attachment #2: Type: text/html, Size: 6386 bytes --]
next prev parent reply other threads:[~2022-07-03 17:49 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 [this message]
2022-07-03 19:48 ` Clem Cole
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).