The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Andy Wallis <>
To: Marc Donner <>
Subject: [TUHS] Re: Were any of the commercial unixes source-available?
Date: Sun, 03 Sep 2023 11:09:50 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 2023-09-03 08:40, Marc Donner wrote:
> My team at Morgan Stanley had a source license to SunOS in the early
> ‘90s.  We tried to secure a license to AIX source but never
> succeeded.

We had access to the AIX source at my work place. The AIX 3.2.5 source 
delivery included a build machine because we had requirements to be able 
to support and redistribute AIX 3.2.5 for up to 20 years. As I recall, 
it required a lot of high level negotiations between us and IBM to get 

Access was limited to select people on an air-gapped machine. The source 
code itself was locked away on 8mm tape and required signatures to check 
it out.

IBM did have a public announcement letter for AIX 3.2.5 source access.

We also had access to the various AIX versions that we had to support 
our government customers. I know we had access to AIX 4.3.3, 5.1,5,2, 
and 5.3 source code. One of our developers would fix bugs that he found 
and file PMRs to tell the AIX developers what exactly to fix. A strip 
command change to support very large executables took 18 months for them 
to fix because they didn't understand why failing to strip very large 
binaries was a problem.
-Andy Wallis

  reply	other threads:[~2023-09-03 15:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-03  5:19 [TUHS] " Joseph Holsten
2023-09-03 10:42 ` [TUHS] " Ron Natalie
2023-09-03 15:48   ` Warner Losh
2023-09-03 11:25 ` Andrew Warkentin
2023-09-03 12:40   ` Marc Donner
2023-09-03 15:09     ` Andy Wallis [this message]
2023-09-03 15:59   ` Warner Losh

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

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