The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: norman@nose.cs.utoronto.ca (Norman Wilson)
Subject: [TUHS] SCO vs. IBM: NOVELL steps up to the plate
Date: Mon,  9 Jun 2003 09:00:31 -0500	[thread overview]
Message-ID: <Dl4tzrT1lQK9.tB6tvnhh@128.100.27.218> (raw)

Kenneth Stailey:

  Two words: "version control".

  If the code that SCO purports is copied into Linux is known
  the version control archives will say who inserted it.  It will
  be very easy to prove if Caldera inserted the code
  themselves.

Alas, two more words: "read-write storage."  Version control
info is stored in a file; how do we know (as SCalderaO might
argue) that some hacker hasn't edited it after the fact to
pretend something was put in by Caldera, or that they just
lied about it to begin with?

Version control data might be a useful, but I suspect only as
a trail to specific people whose could then offer personal
testimony about the history of a particular piece of code.
The testimony would be harder to impeach than the code.

Even a read-only copy of the version control info, e.g. a
CD-ROM, isn't a lot more solid; some hard evidence would
be needed of when that CD-ROM was written, beyond the
easily-forged timestamps on the disc itself, and there could
still be a claim that someone just lied when writing it,
especially if there is a claim that malice was involved.  So
it still would probably come down to personal testimony.

The usual disclaimer applies: I'm no lawyer.  I'm just trying
to think of counter-arguments, both those reasonable in
abstract and those that seem to fit within the spirit of the
complaint against IBM.

Norman Wilson
Toronto ON




             reply	other threads:[~2003-06-09 14:00 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-09 14:00 Norman Wilson [this message]
  -- strict thread matches above, loose matches on Subject: below --
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 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=Dl4tzrT1lQK9.tB6tvnhh@128.100.27.218 \
    --to=norman@nose.cs.utoronto.ca \
    /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).