The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: rob@vetsystems.com (Robert Tillyard)
Subject: [TUHS] SCO vs. IBM: NOVELL steps up to the plate
Date: Thu, 29 May 2003 13:16:33 +0100	[thread overview]
Message-ID: <BAFBB8B1.118%rob@vetsystems.com> (raw)
In-Reply-To: <200305290749.h4T7nu22092199@ducky.net>

I believe the legal action is over breach on contract with IBM and not on
copyright issues.

But if it turns out the IBM is guilty of lifting SCO code and putting it
into Linux I think SCO does have the right to get a bit upset about it,
after all I wouldn't be to happy if I had to compete with a product that's
just about free and contains code that I wrote.

Regards, Rob.

On 29/5/03 8:49 am, "Mike Haertel" <mike at ducky.net> wrote:

>> Here's a question of interest not to the Linux community but to
>> the TUHS one: if, as Novell now claim, the 1995 agreement didn't
>> convey the UNIX copyrights to SCO, under what right did SCO issue
>> the Ancient UNIX Source Code agreements, whether the restrictive
>> version of early 1998 or the do-as-you-like Caldera letter of early
>> 2002?  Are those agreements really valid?
> 
> You can have the right to sublicense something without owning
> the copyright.  You can even have the right to sublicense the
> right to sublicense without owning the copyright, and so on.
> It all depends on your contract with the real copyright holder.
> 
> This is probably how the contract for Novell's "sale" of Unix
> to (old) SCO was written.
> 
> But only the real copyright holder can bring a legal action
> against copyright violators.  And judging from recent press
> releases it would seem that Novell feels it is under no
> contractual obligation to do so on (new) SCO's behalf.




  reply	other threads:[~2003-05-29 12:16 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-28 19:25 Norman Wilson
2003-05-28 23:24 ` Cornelius Keck
2003-05-29  0:02   ` Warren Toomey
2003-05-29  7:49 ` Mike Haertel
2003-05-29 12:16   ` Robert Tillyard [this message]
2003-05-29 12:33     ` M. Warner Losh
2003-05-29 23:50       ` Greg 'groggy' Lehey
2003-05-29 23:56         ` M. Warner Losh
2003-05-30  0:37           ` Greg 'groggy' Lehey
2003-05-30  1:01             ` Warren Toomey
2003-05-30  1:20               ` Greg 'groggy' Lehey
2003-05-29 13:18     ` Kenneth Stailey
  -- strict thread matches above, loose matches on Subject: below --
2003-06-09 14:00 Norman Wilson
2003-06-09 10:20 zmkm zmkm
2003-06-09 15:33 ` Boyd Lynn Gerber
2003-06-08 13:09 Aharon Robbins
2003-06-08 10:32 zmkm zmkm
2003-06-08  9:56 Aharon Robbins
2003-06-09  2:32 ` Kenneth Stailey
2003-05-30  9:01 Wesley Parish
2003-05-30  1:00 Norman Wilson
2003-05-28 12:11 [TUHS] SCO vs. IBM: Eric Raymond striking a blow for ... something Kenneth Stailey
2003-05-28 18:49 ` [TUHS] SCO vs. IBM: NOVELL steps up to the plate 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=BAFBB8B1.118%rob@vetsystems.com \
    --to=rob@vetsystems.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).