The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: grog@lemis.com (Greg Lehey)
Subject: [TUHS] Fwd: Helping in the battle against SCO
Date: Thu, 11 Sep 2003 10:25:46 -0700	[thread overview]
Message-ID: <20030911172545.GC946@adelaide.lemis.com> (raw)
In-Reply-To: <20030911000259.F34D91E83@minnie.tuhs.org>

On Wednesday, 10 September 2003 at 19:59:07 -0400, Norman Wilson wrote:
> I don't see how any diffing we do will make any difference `in the
> battle against SCO.'

It could.  There's a lot of confusion out there.  The people on this
list have a much better understanding of the technical issues than
just about any other group of people I can think of.

> If we find cases in which Linux has incorporated System V licensed
> code, that will certainly be meaningful; but if, as seems likely, we
> don't, SCO can just say their tools are better than hours.

FWIW, the first example that SCO showed in Las Vegas on 18 August does
appear to be derived from System V.3 malloc().  See
http://www.lemis.com/grog/SCO/code-comparison.html for the details.
Also, if anybody else can confirm or deny my analysis based on code
inspection, I'd be *very* grateful.

Summary: the first example showed a slightly modified version of Third
Edition malloc() being used for a slightly different purpose in the
SGI ia64 port only.  The slight modifications tracked those in System
V.3, suggesting that SGI derived their code from System V, and not
from an earlier version.  On the other hand, the differences in System
V.3 were removed again, and in fact the Linux community had already
removed the entire code before SCO "revealed" it.

> And besides, it is SCO who have brought the complaint, so both
> legally and ethically it's up to SCO to prove the case, not up to
> others to disprove it, no matter what fearsome roars SCO emit.

No question.

Greg
--
Finger grog at lemis.com for PGP public key
See complete headers for address and phone numbers


  parent reply	other threads:[~2003-09-11 17:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-10 23:59 Norman Wilson
2003-09-11  0:41 ` Andru Luvisi
2003-09-11 17:32   ` Greg Lehey
2003-09-11 17:25 ` Greg Lehey [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-09-15 20:39 Norman Wilson
2003-09-16  3:01 ` M. Warner Losh
2003-09-10 20:18 Matthew Mastracci
2003-09-10 23:17 ` Warren Toomey
2003-09-09 22:02 Warren Toomey
2003-09-10  1:14 ` Maciek Bieszczad

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=20030911172545.GC946@adelaide.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).