The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: wes.parish@paradise.net.nz (Wesley Parish)
Subject: [TUHS] SCO vs. IBM: NOVELL steps up to the plate
Date: Fri, 30 May 2003 21:01:44 +1200	[thread overview]
Message-ID: <200305302101.44047.wes.parish@paradise.net.nz> (raw)

On Friday 30 May 2003 11:50 am, Greg 'groggy' Lehey wrote:
> On Thursday, 29 May 2003 at  6:33:54 -0600, M. Warner Losh wrote:
> > In message: <BAFBB8B1.118%rob at vetsystems.com>
> >
> >             Robert Tillyard <rob at vetsystems.com> writes:
> >> I believe the legal action is over breach on contract with IBM and
> >> not on copyright issues.
> >
> > All of SCO's statements to the court have been contractual.  Their
> > statements to the press have been inflated to include things that
> > aren't actually alledged in the court filings.
>
> What's not very clear here is that there seem to be two issues.  The
> IBM issue is, as you say, a contractual one which about which they
> have been remarkably vague.  The suspension of Linux distribution is a
> different matter.  From http://www.lemis.com/grog/sco.html:
>
>    On Tuesday, 27 May 2003, I spoke to Kieran O'Shaughnessy, managing
>    director of SCO Australia. He told me that SCO had entrusted three
>    independent companies to compare the code of the UnixWare and Linux
>    kernels. All three had come back pointing to significant
>    occurrences of common code ("UnixWare code", as he put it) in both
>    kernels.
>
>    In view of the long and varied history of UNIX, I wondered whether
>    the code in question might have been legally transferred from an
>    older version of UNIX to Linux, so I asked him if he really meant
>    UnixWare and not System V.4. He stated that it was specifically
>    UnixWare 7.
>
> >> 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.
> >
> > That's the rub.  Do they, in point of fact, actually have any code
> > they own the Copyright to or the patent rights to?
>
> Of course they have lots of code with their own copyright.  The
> release of JFS was one example.  Probably the majority of AIX was
> developed by IBM, not by AT&T.  It's rather similar to the issue with
> 4BSD in the early 90s: with a little bit of work you could probably
> replace the entire AT&T code in AIX and have a system which did not
> require an SCO license.

I would say that that is entirely likely.  AIX was developed by IBM for
IBM-specific machines running in IBM-style environments, and I can imagine
that SysVRx just _doesn't_ _cut_ _the_ _mustard_.

So, SCO's latching on the IBM for Monterey - RS-6000 was 64-bit, or am I
getting confused? - probably gave SCO much more than it gave IBM.  So
ironically, if IBM donated stuff to Monterey under the terms of the agreement
and later incorporated the same stuff into Linux, it _could_ look as if they
had taken stuff from SysVRx/Unixware - stuff that SCO had never had the
opportunity to develop if it hadn't been for Monterey and IBM's pre-existing
expertise.

Just some thoughts - but if that is so, I can see why IBM's not getting too
het up about the whole muck-up.

Wesley Parish

> If you mean "is there IBM copyright code in Linux?", I think the
> answer is again yes, but it's under the GPL or possibly IPL, IBM's
> attempt at a compromise between proprietary licenses and the GPL.  I
> think they've given up on the IPL now.
>
> For what it's worth, I'd be astounded if SCO's claims were found to be
> true.
>
> Greg

--
Mau e ki, "He aha te mea nui?"
You ask, "What is the most important thing?"
Maku e ki, "He tangata, he tangata, he tangata."
I reply, "It is people, it is people, it is people."



             reply	other threads:[~2003-05-30  9:01 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-30  9:01 Wesley Parish [this message]
  -- 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  1:00 Norman Wilson
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
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
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=200305302101.44047.wes.parish@paradise.net.nz \
    --to=wes.parish@paradise.net.nz \
    /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).