From: crossd@gmail.com (Dan Cross)
Subject: [TUHS] RT/PC-centric AIX history
Date: Thu, 9 Mar 2017 22:27:40 -0500 [thread overview]
Message-ID: <CAEoi9W4PD9PhDTNOJ-QE1DFvHSfc-mnVA3pS0i37aRh03nhZ5w@mail.gmail.com> (raw)
In-Reply-To: <06D4621236AA4E76A87D603786775B68@studyvista>
Wow, this is really cool, Charlie. It puts a lot of stuff in perspective.
I wonder if you might add a bit more detail about the BSD ports? That's
what we ran on our RTs; I seem to recall that product was only available to
educational institutions and was referred to as AOS: "Academic Operating
System." I do recall that it came with NFS, and possibly AFS version 2? It
seemed to be approximately 4.3-Tahoe based. The AFS bit is hazy....
On Thu, Mar 9, 2017 at 2:41 PM, Charles H Sauer <sauer at technologists.com>
wrote:
> I've refrained from jumping into AIX & RT/PC discussions on TUHS. It seems
> more appropriate to summarize AIX history than try to correct or clarify
> specifics out of context.
>
> I wrote about 5 pages, got feedback, revised accordingly, and posted at
> https://notes.technologists.com/notes/2017/03/08/lets-start-
> at-the-very-beginning-801-romp-rtpc-aix-versions/.
>
> Charlie
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20170309/57b7675c/attachment.html>
next prev parent reply other threads:[~2017-03-10 3:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-09 19:41 Charles H Sauer
2017-03-09 19:51 ` Clem Cole
2017-03-09 20:14 ` Larry McVoy
2017-03-10 3:55 ` Cory Smelosky
2017-03-10 12:08 ` Jason Stevens
2017-03-10 15:34 ` Dave Horsfall
2017-03-10 0:25 ` Jason Stevens
2017-03-10 3:27 ` Dan Cross [this message]
2017-03-10 4:01 ` Charles H Sauer
2017-03-10 12:09 ` Jason Stevens
2017-03-10 13:13 ` Jacob Goense
2017-03-10 13:15 ` Jason Stevens
2017-03-10 14:05 Noel Chiappa
2017-03-10 20:07 ` Ron Natalie
2017-03-10 20:10 ` Ron Natalie
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=CAEoi9W4PD9PhDTNOJ-QE1DFvHSfc-mnVA3pS0i37aRh03nhZ5w@mail.gmail.com \
--to=crossd@gmail.com \
/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).