From: Anton Shepelev <anton.txt@gmail.com>
To: tuhs@tuhs.org
Subject: [TUHS] Re: Can Ancient Unix be relicensed?
Date: Thu, 17 Oct 2024 02:34:14 +0300 [thread overview]
Message-ID: <20241017023414.834be891f47301195bdfa510@gmail.com> (raw)
In-Reply-To: <CANCZdfpKpdLvfg9t-DixmeRzT3PKHtERcUUJvNSbKHfqXB-vCA@mail.gmail.com>
Warner Losh to Anton Shepelev:
> > 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>
> >
> > [...]
> > 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:
> > [...]
> > That said, is there a chance that the copyright holder
> > of Ancient Will agree to release a similar note
> > regarding everything released under Caldera license?
>
> That's a complicated question.
> [...snipped.but.read...]
Complicated indeed, and to a degree I should not have
expected.
So it was not an arbitrary decision by Caldera to use the
original BSD license? Can they have used the modern three-
clause version with equal ease?
> 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.
No worldly benefit; the bare goodwill is all I can hope for.
> So I'm doubtful. Your best bet is to not make your changes
> available under the GPL.
The four-clause BSD license excludes not only GPL itself,
but (I think) the many GPL-compatible licenses. The
simplest thing for me to do is probably to keep the BSD-like
Caldera license. Thanks for the feedback, Warner!
next prev parent reply other threads:[~2024-10-16 23:34 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 ` [TUHS] " Warner Losh
2024-10-16 23:34 ` Anton Shepelev [this message]
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=20241017023414.834be891f47301195bdfa510@gmail.com \
--to=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).