From: Brad Spencer <brad@anduin.eldar.org>
To: Dan Cross <crossd@gmail.com>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] AOS and IBM/RT [Re: Amdahl UTS, AIX/370, AIX/ESA
Date: Thu, 21 Nov 2019 08:07:00 -0500 [thread overview]
Message-ID: <xon8so9z8cr.fsf@anduin.eldar.org> (raw)
In-Reply-To: <CAEoi9W6Nwj-qMRNoC-bxdxuC7s6E1TSRo3dkzKMnzSxoheLm5g@mail.gmail.com> (message from Dan Cross on Thu, 21 Nov 2019 06:58:38 -0500)
Dan Cross <crossd@gmail.com> writes:
> On Thu, Nov 21, 2019, 1:33 AM Al Kossow <aek@bitsavers.org> wrote:
>
>>
>>
>> On 11/5/19 11:59 PM, SPC wrote:
>> >
>> >
>> > Is it AOS stuff saved and available (including source code)
>> > un some place on the Internet?
>>
>> It was, and may still be in the afs heirarchy
>> I'm not going to say where, or how complete what was there is
>> I also seem to remember it still sat on top of an AIX microkernel
>> and didn't go down to bare metal.
>>
>
> No, that's not true. AOS was basically 4.3BSD Tahoe plus NFS and it ran on
> bare RT hardware. There was source code available to universities, though
> as I recall some bits related to memory management were missing and
> distributed as object files. I gathered, at the time, this was due to some
> obscure intellectual property reasons. People later tried to Port e.g.
> 4.4BSD to aging RT hardware and found it challenging because the memory
> subsystem was so different.
>
> But anyway, there was no hypervisor involved.
>
> - Dan C.
For a brief time a long time ago, I used a 4.3BSD based Mt. Xinu, MACH
microkernel, OS on the IBM-RT as an alternative to AOS. Ran well
enough, but was disk and memory constrained. We had source to much of
the system (or perhaps all of it, don't remember), but I seem to recall
that compiling it was a big pain. Something like you had to use a
specific compiler (perhaps referred to as High C?? hc command perhaps)
to compile some of the source. gcc had a backend for the ROMP
processor, but it had a hard time making usable binaries. I think that
some variation of pcc was the usual compiler. I remember it being
pretty stock 4.3BSD with NFS and minus YP/NIS. We used them mostly as X
terminal workstations.
--
Brad Spencer - brad@anduin.eldar.org - KC8VKS - http://anduin.eldar.org
next prev parent reply other threads:[~2019-11-21 13:28 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-03 21:05 [TUHS] " Kevin Bowling
2019-11-03 23:29 ` Dennis Boone
2019-11-04 0:06 ` Kevin Bowling
2019-11-04 1:29 ` Dennis Boone
2019-11-04 1:58 ` Kevin Bowling
2019-11-04 3:39 ` Gregg Levine
2019-11-04 4:49 ` Kevin Bowling
2019-11-04 15:32 ` Adam Thornton
2019-11-05 16:21 ` Ronald Natalie
2019-11-05 18:04 ` Kevin Bowling
2019-11-05 19:22 ` ron
2019-11-05 17:30 ` Clem Cole
2019-11-05 18:07 ` Kevin Bowling
2019-11-05 18:15 ` Clem Cole
2019-11-05 19:03 ` Christopher Browne
2019-11-05 19:12 ` Kevin Bowling
2019-11-05 19:26 ` SPC
2019-11-05 19:28 ` SPC
2019-11-05 20:26 ` Kevin Bowling
2019-11-05 20:10 ` Clem Cole
2019-11-05 20:42 ` Kevin Bowling
2019-11-05 21:11 ` Clem Cole
2019-11-05 22:11 ` [TUHS] one element of one of M factions of N companies [Re: " Charles H Sauer
2019-11-06 0:06 ` Theodore Y. Ts'o
2019-11-06 3:36 ` Charles H. Sauer
2019-11-06 7:59 ` [TUHS] AOS and IBM/RT " SPC
2019-11-06 15:51 ` Charles H Sauer
2019-11-07 22:40 ` Grant Taylor via TUHS
2019-11-08 4:39 ` Jason Stevens
2019-11-21 6:26 ` Al Kossow
2019-11-21 11:58 ` Dan Cross
2019-11-21 13:07 ` Brad Spencer [this message]
2019-11-21 14:19 ` Dan Cross
2019-11-21 16:16 ` Chet Ramey
2019-11-21 20:53 ` Dan Cross
2019-11-21 16:43 ` greg travis
2019-11-21 19:41 ` arnold
2019-11-21 20:21 ` Jon Steinhart
2019-11-21 17:33 ` Charles H Sauer
2019-11-21 17:36 ` Dan Cross
2019-11-21 18:11 ` Brad Spencer
2019-11-21 17:29 ` Charles H Sauer
2019-11-22 20:38 ` Al Kossow
2019-11-06 20:28 Pat Barron
2019-11-06 20:31 Pat Barron
2019-11-21 19:53 Noel Chiappa
2019-11-21 20:08 ` Clem Cole
2019-11-23 4:40 ` Gregg Levine
2019-11-23 12:51 ` 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=xon8so9z8cr.fsf@anduin.eldar.org \
--to=brad@anduin.eldar.org \
--cc=crossd@gmail.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).