From: Warner Losh <imp@bsdimp.com>
To: Anton Shepelev <anton.txt@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Can Ancient Unix be relicensed?
Date: Wed, 16 Oct 2024 16:55:18 -0600 [thread overview]
Message-ID: <CANCZdfpKpdLvfg9t-DixmeRzT3PKHtERcUUJvNSbKHfqXB-vCA@mail.gmail.com> (raw)
In-Reply-To: <20241017013010.a40487c4e71937a5740caabf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3035 bytes --]
On Wed, Oct 16, 2024, 4:30 PM Anton Shepelev <anton.txt@gmail.com> wrote:
> Hello, all.
>
> In 2002, Caldera released Ancient Unix code under Caldera
> license:
>
> <https://www.tuhs.org/Archive/Caldera-license.pdf>
>
> based on the four-clause BSD license:
>
> <https://spdx.org/licenses/BSD-4-Clause.html>
>
> Consequently, it was used by derived projects, such as
> Traditional Vi:
>
> <https://ex-vi.sourceforge.net/>
>
> This proect having been abandoned and orphaned since 2005, I
> wanted to host it on GNU Savanna and there to breath some
> life into it. Unfortunately, the 4-clause BSD license is
> incompatible with GPL:
>
> <https://www.gnu.org/licenses/license-list.html#OriginalBSD>
>
> The incompatibilty is due entirely to the infamous third
> clause about adverising. Three years prior to Caldera's
> release of old Unix code, The Berkley Univercity removed
> this clause, producing the GNU-compatible modified BSD
> License:
>
> <https://opensource.org/license/BSD-3-clause>
>
> They published a notice to that effect on their FTP:
>
> <ftp://ftp.cs.berkeley.edu/pub/4bsd/README.Impt.License.Change>
>
> Although it has been taken down[1], copies exist all over
> the internet, e.g.:
>
> <
> https://raw.githubusercontent.com/abbrev/punix/refs/heads/master/README.Impt.License.Change
> >
>
> That said, is there a chance that the copyright holder of
> Ancient Will agree to release a similar note regarding
> everying released under Caldera license? If there is, whom
> shall I contact about it? It will benefit everybody using
> Ancient Unix code.
>
That's a complicated question. Does 32V have a valid copyright? Maybe,
maybe not. There is a preliminary ruling suggesting no that effectively
forced AT&T to settle with the Regents, but it was never finalized. There's
good reasons to believe its logic and fact pattern would apply to 7th
edition and maybe 6th.
Putting that aside, there has been a dispute over what copyrights
transferred from Novell to SCO. A judge said no for System V, undermining
SCO's case. But older copyrights weren't explivitly named, but the same
thing: the facts patterns for System V likely applied to older Unix.
So, Novell's assets have been sold 4 times or more. Finding the right
people inside the current company to talk to is hard. It's not their
promary business. It's not clear how many rights they have. It's hard to
show how it could benefit them. And even if you could, another sale might
happen in the mean time.
People have been teying to get even a statement that old SCO legitimately
granted the Ancient license to no avail.
So I'm doubtful. Your best bet is to not make your changes available under
the GPL. They cut against the spirit of 4 clause BSD and step in the middle
of a very old Stallman vs Berkeley dispute from the 4.2 era...
At this point, it's a mess
Warner
____________________
> 1. Why the murrain of FTP servers all over the world?
>
>
[-- Attachment #2: Type: text/html, Size: 4794 bytes --]
next prev parent reply other threads:[~2024-10-16 22:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 22:30 [TUHS] " Anton Shepelev
2024-10-16 22:55 ` Warner Losh [this message]
2024-10-16 23:34 ` [TUHS] " Anton Shepelev
2024-10-16 23:58 ` segaloco via TUHS
2024-10-17 3:57 ` Chris Hanson
2024-10-17 4:01 ` Chris Hanson
2024-10-17 13:51 ` Ron Natalie
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=CANCZdfpKpdLvfg9t-DixmeRzT3PKHtERcUUJvNSbKHfqXB-vCA@mail.gmail.com \
--to=imp@bsdimp.com \
--cc=anton.txt@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).