The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: sauer@technologists.com (Charles H Sauer)
Subject: [TUHS] RT/PC-centric AIX history
Date: Thu, 9 Mar 2017 22:01:36 -0600	[thread overview]
Message-ID: <22C6D328D23F4DBFA28210996351B64C@studyvista> (raw)
In-Reply-To: <CAEoi9W4PD9PhDTNOJ-QE1DFvHSfc-mnVA3pS0i37aRh03nhZ5w@mail.gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2542 bytes --]

Dan,

I’m not sure how well I can answer, but I’ll try.

I think the responsible organization was known as ACIS (ACademic Information Systems??), with BSD work primarily staffed in the Palo Alto Scientific Center. Back then IBM had “scientific centers” separate from the Research Division – my main contact was with Cambridge, MA and Palo Alto centers, but I think there were 13 centers world wide.

I think you’re correct that it was called AOS and likely correct that it was only available to academic institutions. I was primarily aware of usage at Brown, CMU and MIT.

The sole RT I had with AOS was at my house, and I didn’t have Internet access at the office, much less at home, so though I was in the thick of the distributed filesystem work, didn’t do any of it hands on on AOS.

I was technically responsible for getting the NFS license for AIX and I think you’re right that ACIS put NFS on AOS once we had the license, but would have forgotten that if you hadn’t reminded me. I think the license agreement was put in place in the second half of 1988, but that could easily be off by months or longer.

Certainly much of the Andrew work in general and AFS specifically was done with AOS. I assume that all AFS versions were made available on AOS as soon as Kazar et al thought they were ready.

Charlie

From: Dan Cross 
Sent: Thursday, March 09, 2017 9:27 PM
To: Charles H Sauer 
Cc: TUHS 
Subject: Re: [TUHS] RT/PC-centric AIX history

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/bf82fd6e/attachment-0001.html>


  reply	other threads:[~2017-03-10  4:01 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
2017-03-10  4:01   ` Charles H Sauer [this message]
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=22C6D328D23F4DBFA28210996351B64C@studyvista \
    --to=sauer@technologists.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).