The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: peter.jeremy@alcatel.com.au (Peter Jeremy)
Subject: [TUHS] SCO removed the anchient UNIX offer web page
Date: Fri, 20 Jun 2003 11:52:47 +1000	[thread overview]
Message-ID: <20030620015247.GF273@gsmx07.alcatel.com.au> (raw)
In-Reply-To: <Pine.LNX.4.44.0306191709510.485-100000@gladen>

On 2003-Jun-19 17:10:52 -0700, Andru Luvisi <luvisi at andru.sonoma.edu> wrote:
>On Fri, 20 Jun 2003, Warren Toomey wrote:
>[snip]
>> I would be very careful here. At the very least, the contract doesn't
>> explicitly cover SysIII, although you could argue that it is a
>> SUCCESSOR OPERATING SYSTEM. And the Caldera license explicitly forbids
>> SysIII.
>
>It seems to me that the fact that SCO offered SysIII on the page linked to
>from the license agreement implies that SCO intended for SysIII to be
>covered by this license.

I think the status of SysIII was always a bit murky.  Whilst it may
have been old SCO's intention that the Ancient UNIX license covered
SysIII, the license doesn't say so.  Since the license doesn't
explicitly allow SysIII, it would be up to you to convince the judge
that the license does implicitly cover SysIII.

Of course, by publishing SysIII, SCO have blown any trade secret claims
relating to SysIII out of the water.  But that doesn't make it legal
for you to use it.

Peter


  reply	other threads:[~2003-06-20  1:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-19 23:31 Kenneth Stailey
2003-06-19 23:35 ` Kenneth Stailey
2003-06-19 23:56   ` Warren Toomey
2003-06-20  0:10     ` Andru Luvisi
2003-06-20  1:52       ` Peter Jeremy [this message]
2003-06-20  0:57   ` Gregg C Levine
2003-06-20  7:01     ` Warren Toomey
2003-06-20  3:00   ` Gregg C Levine
2003-06-20 15:18     ` Kenneth Stailey

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=20030620015247.GF273@gsmx07.alcatel.com.au \
    --to=peter.jeremy@alcatel.com.au \
    /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).