The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Warner Losh <imp@bsdimp.com>
To: Dan Cross <crossd@gmail.com>
Cc: TUHS <tuhs@tuhs.org>
Subject: [TUHS] Re: Open sourcing SunOS?
Date: Wed, 22 Feb 2023 13:04:37 -0700	[thread overview]
Message-ID: <CANCZdfoq2B0Tgm-GzOYTw2hRsbh4x4Wi_L7c9U5zaXVk8uYBiw@mail.gmail.com> (raw)
In-Reply-To: <CAEoi9W7fiY4T=N2KzjpH0Rujp-tb-fX5dyS4rVgVPq4AGipuHQ@mail.gmail.com>

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

On Wed, Feb 22, 2023, 8:50 AM Dan Cross <crossd@gmail.com> wrote:

> Has anyone tried talking to anyone at Oracle about possibly getting
> the SunOS code released under an open source license? There can't be
> any commercial value left in it.
>

SunOS 4 has a lot of encumbered code in it, especially for i386 drivers.
Bits of the
network stack as well. It was hopeless to try to open source. There was a
lot of bits
and pieces that Sun had done with contracts that were, at best, ambiguous
for
what to do should they want to open source it. At least that's the story
I've heard
from people at Sun, both engineers and management.

I know when Solbourne did their OS/MP 4.0 and 4.1 SunOS MP system, there
was a lot of back and forth between Solbourne's and Sun's lawyers to get all
the pieces needed to build the system. For example, initially SunView was
not
included in the offering, so my group was formed to write our clone for it
(This
would become OI (Object Interface) and uib (User Interface Builder) that we
did in C++ to allow it to present in either Motif or OpenLook).

I also know that Sun tried to donate their VM system to Berkeley btween
BSD4.3
and BSD4.4. Had the support of Scott McNeely and was almost a done deal.
However,
the lawyers said that the company would need to take a 'write down' loss on
the
donation, which would likely tank the stock price of Sun, so it was nixed.
So instead,
Berkeley did the next best thing (really the only available thing) and went
with the
MachVM.

One can find the sources to 4.1.4 and 4.1.3 online (though not the earlier
4.1.1 or
4.0.x which have the i386 port in it). The newer sources do have i386 bits,
but from
my cursory investigation, it's mostly remnants of the support. Of course,
if one were
to modify this, and try to distribute it, you'd likely be asking for
trouble. At least two
of the abandonware sites have copies. There's also something purporting to
the the
SCCS files for the system, but alas, they are not actually there.

Having talked to the VPs that got OpenSolaris released about doing SunOS
(after
they'd left Sun, I worked for them), it was clear that OpenSolaris was hard
enough.
SunOS 4 was too old by even the point to get all the successors in interest
to
agree to modifications of the old contracts to allow source distribution
without
significant restrictions to agree to make enough of the system available
for it to
be interesting to people.

Oracle has pulled back from OpenSolaris, fired all the Solaris engineers
and has
all that on basically life support. I doubt they'd want to do anything for
even that
modern code base, let alone something that's ancient history, would be hard
to find,
would be difficult to find the old paperwork for it to clear legal, etc.

So, I'm not at all optimistic this could ever happen prior to the
expiration of the
copyrights of the original code.

Warner

        - Dan C.
>

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

  parent reply	other threads:[~2023-02-22 20:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-22 15:49 [TUHS] " Dan Cross
2023-02-22 16:23 ` [TUHS] " Robert Clausecker
2023-02-22 16:30   ` Dan Cross
2023-02-22 19:52     ` Dave Horsfall
2023-02-22 20:04 ` Warner Losh [this message]
2023-02-22 20:12   ` Larry McVoy
2023-02-22 20:44     ` Brad Spencer
2023-02-22 20:46     ` Warner Losh
2023-02-22 20:54       ` Larry McVoy
2023-02-23  0:12   ` Rob Gingell
2023-02-23  2:14     ` Warner Losh
2023-02-23  7:22       ` Rob Gingell

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=CANCZdfoq2B0Tgm-GzOYTw2hRsbh4x4Wi_L7c9U5zaXVk8uYBiw@mail.gmail.com \
    --to=imp@bsdimp.com \
    --cc=crossd@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).