From: Warner Losh <imp@bsdimp.com>
To: Ron Natalie <ron@ronnatalie.com>
Cc: Tautological Eunuch Horticultural Scythians <tuhs@tuhs.org>
Subject: [TUHS] Re: Were any of the commercial unixes source-available?
Date: Sun, 3 Sep 2023 09:48:43 -0600 [thread overview]
Message-ID: <CANCZdfpWo5nr4CkM6gZ7+ZwycZ-=DqCo6e8eEJJ4MhK-uy0i2Q@mail.gmail.com> (raw)
In-Reply-To: <emeb8aaf51-e8f6-4d72-a007-733e64e7e5a2@08efa2db.com>
[-- Attachment #1: Type: text/plain, Size: 1242 bytes --]
On Sun, Sep 3, 2023, 4:42 AM Ron Natalie <ron@ronnatalie.com> wrote:
> Note that most UNIX was protected by Trade Secret rather than copyright
> so there’s no statutory expiration date.
>
But only so long as they remain secret... there are a few leaks of early
stuff in bitsavers... the leader broke the law, perhaps, but once the
secret is out there, its no longer secret. See the 32V preliminary rulings
for variations on that theme. System V and newer did have copyright
protection as well as trade secret contract stuff...
It isn't hard to find at least one copy of most of the major and many minor
players. It's fair use to copy for study and commentary. But building a
full system for commercial benefit is not.
We were contractors for IBM so we had XENIX and AIX sources in our
> facility under NDAs, so I don’t believe IBM dealt with it other than
> OCO.
> I did have a license for the source code for Interactive Systems IS/1
> but that was a fairly straight forward System V kernel.
>
Several variations on that are out there...
What isn't out there are the full source code control trees. At least Sun
distributed them. But so far only a symlink farm for that has been found.
Warner
>
>
[-- Attachment #2: Type: text/html, Size: 2116 bytes --]
next prev parent reply other threads:[~2023-09-03 15:49 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 [this message]
2023-09-03 11:25 ` Andrew Warkentin
2023-09-03 12:40 ` Marc Donner
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='CANCZdfpWo5nr4CkM6gZ7+ZwycZ-=DqCo6e8eEJJ4MhK-uy0i2Q@mail.gmail.com' \
--to=imp@bsdimp.com \
--cc=ron@ronnatalie.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).