The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: Bakul Shah <bakul@iitbombay.org>
Cc: steve jenkin <stevej098@gmail.com>, TUHS <tuhs@tuhs.org>,
	Marc Donner <marc.donner@gmail.com>
Subject: [TUHS] Re: Thoughts on Licenses
Date: Sun, 3 Jul 2022 12:26:25 -0400	[thread overview]
Message-ID: <CAC20D2OWM1X-fM-3j0f4Ri_2bQ3PyzU4xxovjnSENnUP8GNY1Q@mail.gmail.com> (raw)
In-Reply-To: <5E49BE69-8869-473A-B3F5-6744566700F0@iitbombay.org>

[-- Attachment #1: Type: text/plain, Size: 1656 bytes --]

On Sun, Jul 3, 2022 at 11:30 AM Bakul Shah <bakul@iitbombay.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.

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).

 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.

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.
ᐧ
ᐧ

[-- Attachment #2: Type: text/html, Size: 3979 bytes --]

  reply	other threads:[~2022-07-03 16:28 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 [this message]
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
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

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=CAC20D2OWM1X-fM-3j0f4Ri_2bQ3PyzU4xxovjnSENnUP8GNY1Q@mail.gmail.com \
    --to=clemc@ccc.com \
    --cc=bakul@iitbombay.org \
    --cc=marc.donner@gmail.com \
    --cc=stevej098@gmail.com \
    --cc=tuhs@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).