The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Miod Vallat <miod@online.fr>
To: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] First Unix-like OSes not derived from AT&T code?
Date: Mon, 2 May 2022 14:14:04 +0000	[thread overview]
Message-ID: <Ym/nLP7r1tt3AGt3@tarentaine.gentiane.org> (raw)
In-Reply-To: <CAEoi9W4HYmH+cBdyPyrSTZWe+LR6J9sEbjyOUGj-q_N-7FPFnQ@mail.gmail.com>

> The RT 4.3 port was called AOS (for the, "Academic Operating System"). It
> was mostly Tahoe with NFS and came with most of the sources, but some bits
> were distributed only as object code: I believe some of the MM bits?
> Perhaps the MMU code? I vaguely recall this being one of the things people
> had a hard time with when trying to port Reno and 4.4 to the RT.

What was delivered as binary was the Advanced Floating-Point Accelerator
microcode.

At the end of the AOS work circa 1996, most of the kernel was 4.4,
except for the network stack which was 4.3-Reno, and the VM system which
was still 4.3 (hence no mmap).

> The port was fairly faithful; the C compiler was a bit strange "High C" or
> "Hi C", bit GCC was available after a while, but had some bug and could not
> compile the kernel.

The compiler was Metaware High C. GCC could not be used to compile the
kernel sources unchanged, because one of the locore->trap.c paths was
relying upon the stack layout used by the compiler. With that fixed, gcc
could be used to build a working kernel.

Miod

  reply	other threads:[~2022-05-02 14:15 UTC|newest]

Thread overview: 79+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-01  9:30 Andrew Warkentin
2022-05-01 11:43 ` Ron Natalie
2022-05-01 11:56   ` Rob Pike
2022-05-01 14:03     ` Kenneth Goodwin
2022-05-03  4:37       ` Jim Carpenter
2022-05-01 14:09   ` Kenneth Goodwin
2022-05-01 18:08     ` ron minnich
2022-05-01 18:22       ` Charles H Sauer (he/him)
2022-05-01 19:49         ` Dan Stromberg
2022-05-01 20:37           ` Charles H Sauer (he/him)
2022-05-02  2:08       ` Kenneth Goodwin
2022-05-02  9:21         ` Dr Iain Maoileoin
2022-05-02 20:19           ` Rich Morin
2022-05-02 21:30             ` Clem Cole
2022-05-02 21:36             ` Dan Cross
2022-05-10 15:28         ` Mary Ann Horton
2022-05-10 16:08           ` Warner Losh
2022-05-10 16:40             ` Heinz Lycklama
2022-05-10 16:42             ` James Frew
2022-05-14  2:56             ` Mary Ann Horton
2022-05-10 16:59           ` Clem Cole
2022-05-10 17:18             ` Clem Cole
2022-05-10 18:05               ` Charles H Sauer (he/him)
2022-05-10 19:27                 ` Lars Brinkhoff
2022-05-10 19:08               ` Henry Bent
2022-05-10 19:33                 ` Richard Salz
2022-05-10 20:18                   ` Ronald Natalie
2022-05-11 16:20                     ` James Frew
2022-05-11 16:51                       ` Paul Winalski
2022-05-10 20:28                   ` Henry Bent
2022-05-10 20:43                   ` Warner Losh
2022-05-10 20:46                   ` Clem Cole
2022-05-11 16:44                     ` Paul Winalski
2022-05-11 17:09                       ` Clem Cole
2022-05-11 17:35                       ` Larry McVoy
2022-05-12  0:16                         ` George Michaelson
2022-05-13  2:46                         ` Adam Thornton
2022-05-15  0:48                           ` Larry McVoy
2022-05-15  5:36                             ` Adam Thornton
2022-05-15 13:37                               ` Larry McVoy
2022-05-12  5:22                       ` Warner Losh
2022-05-12 12:06                         ` Ron Natalie
2022-05-12 12:43                           ` John Cowan
2022-05-15  2:00         ` Stuart Remphrey
2022-05-02  2:42       ` Phil Budne
2022-05-02  6:46         ` Ron Natalie
2022-05-02 13:50           ` Clem Cole
2022-05-02 14:46             ` tytso
2022-05-02 15:38               ` Clem Cole
2022-05-02 20:31                 ` Warner Losh
2022-05-03  5:01                   ` tytso
2022-05-03 11:35                     ` Richard Salz
2022-05-02 23:30           ` Gregg Levine
     [not found]           ` <CAK7dMtD08weh+97mx+ncrq0cxprKgke42C0vFYNPnBkd8Fx9Sg@mail.gmail.com>
2022-05-03  7:28             ` Ronald Natalie
2022-05-02 12:59         ` Kenneth Goodwin
2022-05-02 14:13           ` Richard Salz
2022-05-02 13:14         ` tytso
2022-05-02 13:32           ` Larry McVoy
2022-05-02 13:16         ` Dan Cross
2022-05-02 14:14           ` Miod Vallat [this message]
2022-05-02 14:50             ` ron minnich
2022-05-02 16:13             ` Al Kossow
2022-05-02 18:46               ` Miod Vallat
2022-05-02 19:54               ` Chet Ramey
2022-05-02 21:17             ` Dan Cross
2022-05-02 23:49               ` George Michaelson
2022-05-03  7:22                 ` Ronald Natalie
2022-05-03  7:40               ` Miod Vallat
2022-05-03  8:03                 ` Ron Natalie
     [not found]               ` <CAEoi9W4eD8AF=FwjMT-KPRfyYgD+qgVvE1u3sBwiovm4=1WWLg@mail.g mail.com>
2022-05-03 12:14                 ` John Foust via TUHS
2022-05-01 20:55 ` Michael Huff
2022-05-03  4:55   ` Jim Carpenter
2022-05-02 15:43 ` Clem Cole
2022-05-02 16:16   ` Bakul Shah
2022-05-02 16:19     ` Bakul Shah
2022-05-02 17:14       ` Clem Cole
2022-05-02 16:29     ` Larry McVoy
2022-05-02 17:42     ` Clem Cole
2022-05-02 17:59       ` Bakul Shah

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=Ym/nLP7r1tt3AGt3@tarentaine.gentiane.org \
    --to=miod@online.fr \
    --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).