From: Rob Gingell <gingell@computer.org>
To: Warner Losh <imp@bsdimp.com>, Dan Cross <crossd@gmail.com>
Cc: TUHS <tuhs@tuhs.org>
Subject: [TUHS] Re: Open sourcing SunOS?
Date: Wed, 22 Feb 2023 16:12:23 -0800 [thread overview]
Message-ID: <170a8b0c-4fcb-9069-aeac-5dda72a7eeea@computer.org> (raw)
In-Reply-To: <CANCZdfoq2B0Tgm-GzOYTw2hRsbh4x4Wi_L7c9U5zaXVk8uYBiw@mail.gmail.com>
On 2/22/23 12:04 PM, Warner Losh wrote:
> SunOS 4 has a lot of encumbered code in it, ...
SunOS had a complicated set of license encumbrances. I can't claim to
have fully understood them even at the time. In the mid-1980s, the
notion of "open sourcing" as we understand it today wasn't a goal or
even considered and so never entered into the terms of the technologies
Sun used. These might have been overcome with effort but in the context
of the time it didn't seem important.
Things Sun licensed widely, like source kits for NFS/VFS, were things we
routinely and repeatedly sanitized as they evolved.
As part of the SPARC partners program SunOS was licensed to people
building SPARC-based products but as Warner notes in the Solbourne
experience, especially early on, there wasn't a "product" so much as a
"process" that disseminated it.
> I also know that Sun tried to donate their VM system to Berkeley btween
> BSD4.3
> and BSD4.4.
It would be more correct to say that Sun was willing to donate the VM
system back to Berkeley, but my recollection is that CSRG planned to get
to that functionality through a different implementation path and didn't
want it.
We expected "everyone" to eventually get the VM system, as it was in
SVR4 before SunOS 4.0 even shipped, and so "everyone" (even the people
who otherwise offered BSD systems) would have access to it, just like we
did. (Of course that notion of "everyone" is pretty limited but at the
time it was just The Way It Was.)
We did donate all the shared library work to Berkeley, probably the
closest to what we'd now call "open source" that Sun did in that era. At
the time, Berkeley didn't plan on migrating off of the a.out object file
format and so it was useful to them to have the a.out-based implementation.
> 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.
While I am confident he would have supported it, I doubt Scott ever knew
about the donations and discussions. The organization-chart-local VP
signed off on it and I had a 10 minute phone conversation (no part of
which involved balance sheets or stock values) with the lawyer who wrote
the letter of transmittal that accompanied the code.
next prev parent reply other threads:[~2023-02-23 0:12 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
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 [this message]
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=170a8b0c-4fcb-9069-aeac-5dda72a7eeea@computer.org \
--to=gingell@computer.org \
--cc=crossd@gmail.com \
--cc=imp@bsdimp.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).