The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Marc Donner <marc.donner@gmail.com>
To: Andrew Warkentin <andreww591@gmail.com>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Were any of the commercial unixes source-available?
Date: Sun, 3 Sep 2023 08:40:59 -0400	[thread overview]
Message-ID: <CALQ0xCAPX_C+CC9+KRzArtGaoMYPCyiW7qA4tP8rtdKJXeA0LQ@mail.gmail.com> (raw)
In-Reply-To: <CAD-qYGqWKYqy2f5DSgf--Kee0bSAdYrgOnTpoOjSCefE4QAk7Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2131 bytes --]

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.

On Sun, Sep 3, 2023 at 7:26 AM Andrew Warkentin <andreww591@gmail.com>
wrote:

> On 9/2/23, Joseph Holsten <joseph@josephholsten.com> wrote:
> > I’ve been playing around trying to link the OpenSolaris launch commit to
> > various pieces in the Unix History Repository, and it’s making me wonder
> if
> > we’ll ever have a chance to see the history of the systems.
> >
> > I’m less concerned about HPUX, AIX and SCO’s offerings since I presume
> > someone has copy inside these companies. But what about A/UX, Irix,
> Tru64?
> > Did these ever get sold with licenses to source tapes? Are there copies
> we
> > need to preserve in-camera so something can exist 120 years after
> creation
> > or whenever copyright expires?
> >
> There are source leaks for quite a few commercial Unices floating
> around in various places. These are the ones I'm aware of:
>
> A/UX (0.7, which is complete, and 2.x, which is only the kernel)
> AIX 4.1.3 (most of the kernel and some of user space, possibly
> complete enough to build)
> BSD/OS (various versions, probably complete)
> DEC OSF/1 (1.0 and 2.0; these seem reasonably complete)
> DYNIX 3.x (several versions, possibly complete enough to build)
> DYNIX/PTX (4.x?; possibly complete enough to build)
> IRIX 6.5.5 (missing quite a few major packages and nowhere near
> complete enough to build)
> MIPS RISC/os 4.52 (possibly complete)
> SGI System V GL2-W3.7 (for the IRIS 3000 68K machines; probably complete)
> SunOS 4.1.3 (seems to be the complete base system)
> System V for the 3b2 (several 3.x versions, possibly complete)
> System V for the UNIX PC (3.51, possibly complete)
> System V/386 4.2 (possibly complete)
> ULTRIX-11 (at least 3.1)
> ULTRIX-32 (2.0, which has been confirmed to build by someone else, and
> 4.2, which is also fairly complete)
>
> I haven't looked at any of these in depth, so I'm not completely sure
> of the status of any of them except for A/UX and ULTRIX
>

[-- Attachment #2: Type: text/html, Size: 2628 bytes --]

  reply	other threads:[~2023-09-03 12:41 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 [this message]
2023-09-03 15:09     ` Andy Wallis
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:
  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=CALQ0xCAPX_C+CC9+KRzArtGaoMYPCyiW7qA4tP8rtdKJXeA0LQ@mail.gmail.com \
    --to=marc.donner@gmail.com \
    --cc=andreww591@gmail.com \
    --cc=tuhs@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).