The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Douglas McIlroy <douglas.mcilroy@dartmouth.edu>
To: TUHS main list <tuhs@tuhs.org>
Subject: [TUHS] IBM's involvement (was: SCO's "evidence" (was: RIP Darl McBride former CEO of SCO))
Date: Tue, 5 Nov 2024 08:40:44 -0500	[thread overview]
Message-ID: <CAKH6PiV_ogGZ_PNzmwsXvQu=z-Bsg0pePB2w9zkJnC8AkkhE-w@mail.gmail.com> (raw)

As a bit-part expert witness for the other side of the SCO case, I saw
hundreds of pages of evidence in the form of side-by-side code
comparison. As I recall, the vast majority of highlighted
correspondences were small snippets, often rearranged. I didn't
interact with the lawyers enough to form a solid opinion about where
this stood on the spectrum of coincidence to fair use to plagiarism.
It certainly wasn't wholesale copying. I do not recall being asked to
opine on whether trade secrets had been stolen.

Apropos of rearranged snippets, one of the diff algorithms I
experimented with in the mid-70s identified rearrangements. I
abandoned it because real life code contains lots of similar lines, so
many in PDP-11 assembler programs as to suggest that these programs
are largely permutations of each other. The phenomenon is much less
common in C, but still present; witness the prevalence of code like
      int i, n;
      for(i=0; i<n; i++) {
The phenomenon may have been afoot in the SCO evidence.

In regard to trade secrets, I was surprised when I moved from Unix at
Bell Labs to Linux at Dartmouth and found calendar(1) to be completely
rewritten, but with logic absolutely identical to the original version
I wrote at the Labs. That was so idiosyncratic that the identity of
the two could not have been an accident.

Doug

             reply	other threads:[~2024-11-05 13:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-05 13:40 Douglas McIlroy [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-04  1:17 [TUHS] RIP Darl McBride former CEO of SCO Will Senn
2024-11-04  2:31 ` [TUHS] " Greg 'groggy' Lehey
2024-11-04  3:34   ` Wesley Parish
2024-11-04 17:35     ` Marc Rochkind
2024-11-04 22:50       ` [TUHS] SCO's "evidence" (was: RIP Darl McBride former CEO of SCO) Greg 'groggy' Lehey
2024-11-05  0:05         ` [TUHS] " Marc Rochkind
2024-11-05  1:31           ` [TUHS] IBM's involvement (was: SCO's "evidence" (was: RIP Darl McBride former CEO of SCO)) Greg 'groggy' Lehey

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='CAKH6PiV_ogGZ_PNzmwsXvQu=z-Bsg0pePB2w9zkJnC8AkkhE-w@mail.gmail.com' \
    --to=douglas.mcilroy@dartmouth.edu \
    --cc=tuhs@tuhs.org \
    /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).