From: grog@lemis.com (Greg 'groggy' Lehey)
Subject: [TUHS] SCO sues IBM?
Date: Tue, 11 Mar 2003 16:31:43 +1030 [thread overview]
Message-ID: <20030311060143.GQ45912@wantadilla.lemis.com> (raw)
In-Reply-To: <3394dec0a229ed7a184b5282445bb41e@plan9.bell-labs.com>
On Tuesday, 11 March 2003 at 0:25:40 -0500, Dennis Ritchie wrote:
> A working link to the ancient-Unix license exists at
>
> http://shop.caldera.com/caldera/ancient.html
>
> This is a saved link; I didn't investigate how
> to find it currently from a Caldera or SCO site.
This is the prior license. It contains wording like:
2.1 (a) CALDERA INTERNATIONAL, INC. grants to LICENSEE a personal,
nontransferable and nonexclusive right to use, in the
AUTHORIZED COUNTRY, each SOURCE CODE PRODUCT identified in
Section 3 of this AGREEMENT, solely for personal use (as
restricted in Section 2.1(b)) and solely on or in conjunction
with DESIGNATED CPUs, and/or Networks of CPUs, licensed by
LICENSEE through this SPECIAL SOFTWARE LICENSE AGREEMENT for
such SOURCE CODE PRODUCT. Such right to use includes the right
to modify such SOURCE CODE PRODUCT and to prepare DERIVED
BINARY PRODUCT based on such SOURCE CODE PRODUCT, provided
that any such modification or DERIVED BINARY PRODUCT that
contains any part of a SOURCE CODE PRODUCT subject to this
AGREEMENT is treated hereunder the same as such SOURCE CODE
PRODUCT. CALDERA INTERNATIONAL, INC. claims no ownership
interest in any portion of such a modification or DERIVED
BINARY PRODUCT that is not part of a SOURCE CODE PRODUCT.
That's not the BSD-like license under which they re-released the code
last year.
Greg
--
Finger grog at lemis.com for PGP public key
See complete headers for address and phone numbers
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20030311/0efb01f6/attachment.sig>
next prev parent reply other threads:[~2003-03-11 6:01 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-11 5:25 Dennis Ritchie
2003-03-11 6:01 ` Greg 'groggy' Lehey [this message]
2003-03-12 4:34 ` Jeffrey Sharp
-- strict thread matches above, loose matches on Subject: below --
2003-03-10 21:52 Wesley Parish
2003-03-10 1:21 Greg 'groggy' Lehey
2003-03-10 2:33 ` David C. Jenner
2003-03-10 3:28 ` Peter Jeremy
2003-03-10 20:23 ` Jeffrey Sharp
2003-03-10 3:13 ` Michael Davidson
2003-03-10 20:21 ` Jeffrey Sharp
2003-03-10 21:15 ` Peter Jeremy
2003-03-10 21:54 ` David C. Jenner
2003-03-10 23:45 ` Greg 'groggy' Lehey
2003-03-11 0:22 ` Peter Jeremy
2003-03-11 1:14 ` Gregg C Levine
2003-03-11 1:51 ` Warren Toomey
2003-03-11 1:59 ` Greg 'groggy' Lehey
2003-03-11 3:51 ` Warren Toomey
2003-03-11 4:11 ` Michael Davidson
2003-03-11 9:44 ` Sven Mascheck
2003-03-11 15:40 ` Gregg C Levine
2003-03-12 4:05 ` Jeffrey Sharp
2003-03-12 4:46 ` Jeffrey Sharp
2003-03-12 5:03 ` Greg 'groggy' Lehey
2003-03-12 20:31 ` Peter Jeremy
2003-03-12 20:33 ` Wm. G. McGrath
2003-03-11 3:51 ` Wm. G. McGrath
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=20030311060143.GQ45912@wantadilla.lemis.com \
--to=grog@lemis.com \
/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).