The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: wkt@minnie.tuhs.org (Warren Toomey)
Subject: [TUHS] SCO & Caldera?
Date: Wed, 12 Mar 2003 09:27:13 +1000	[thread overview]
Message-ID: <20030311232713.GA7295@minnie.tuhs.org> (raw)
In-Reply-To: <20030311224500.GV45912@wantadilla.lemis.com>

On Wed, Mar 12, 2003 at 09:15:00AM +1030, Greg 'groggy' Lehey wrote:
> > FWIW I too paid $100 for an ancient Unix license, and I've got the
> > System III stuff that licensees had access to.
> 
> Hmmm.  That's a point.  Does the Ancient UNIX license cover more than
> last year's release?
> Greg

The US$100 SCO Ancient UNIX license had this clause:

    The SOURCE CODE PRODUCTS to which SCO grants rights under this
    Agreement are restricted to the following UNIX Operating Systems,
    including SUCCESSOR OPERATING SYSTEMs, that operate on the 16-Bit
    PDP-11 CPU and early versions of the 32-Bit UNIX Operating System
    with specific exclusion of UNIX System V and successor operating
    systems:

    16-Bit  UNIX Editions 1, 2, 3, 4, 5, 6, 7 
    32-bit  32V

    [ http://minnie.tuhs.org/PUPS/sco_license.txt ]

This implies that System III on the PDP11 is covered by this license,
as SCO has the legal rights to System III and it is a SUCCESSOR
OPERATING SYSTEM.

The BSD-style Caldera license has this clause:

   The source code for which Caldera International, Inc. grants rights are
   limited to the following UNIX Operating Systems that operate on the
   16-Bit PDP-11 CPU and early versions of the 32-Bit UNIX Operating System,
   with specific exclusion of UNIX System III and UNIX System V and
   successor operating systems:

   32-bit  32V UNIX
   16 bit  UNIX Versions 1, 2, 3, 4, 5, 6, 7

   [ http://www.tuhs.org/Archive/Caldera-license.pdf ]

So the new license specifically prohibits System III, whereas the Ancient UNIX
license implicitly permitted System III.

	Warren



  reply	other threads:[~2003-03-11 23:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-11  8:43 Aharon Robbins
2003-03-11 22:45 ` Greg 'groggy' Lehey
2003-03-11 23:27   ` Warren Toomey [this message]
2003-03-11 23:48     ` Greg 'groggy' Lehey
2003-03-12  6:43   ` Lars Brinkhoff
2003-03-18 22:36 Christian Groessler
2003-03-18 22:52 ` Gregg C Levine
2003-03-18 23:10 ` Warren Toomey
2003-03-18 23:29   ` Gregg C Levine
2003-03-19  1:24     ` Warren Toomey
     [not found]   ` <Pine.LNX.4.44.0303181530250.17703-100000@gladen>
2003-03-19  1:22     ` Warren Toomey
2003-03-18 23:22 ` Jon Snader

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=20030311232713.GA7295@minnie.tuhs.org \
    --to=wkt@minnie.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).