From: grog@lemis.com (Greg Lehey)
Subject: [TUHS] Fwd: Helping in the battle against SCO
Date: Thu, 11 Sep 2003 10:32:32 -0700 [thread overview]
Message-ID: <20030911173232.GD946@adelaide.lemis.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0309101738100.2092-100000@gladen>
On Wednesday, 10 September 2003 at 17:41:49 -0700, Andru Luvisi wrote:
> On Wed, 10 Sep 2003, Norman Wilson wrote:
>> I don't see how any diffing we do will make any difference
>> `in the battle against SCO.'
> [snip]
>
> Some ways that I can see it being a good thing to do:
>
> If SCO holds up a piece of common code and the good guys have no
> response, that is bad.
Agreed. That doesn't apply to either piece of code they've shown so
far. This is http://www.lemis.com/grog/SCO/code-comparison.html
again.
> If SCO holds up a piece of common code and the good guys already
> know that it actually came from BSD, and are prepared to
> demonstrate such, that is good.
That's the second example :-) The question I've asked SCO is: how
could you have missed the Berkeley license agreement at the beginning
of this file? SCO have backed off claiming that this is System V
code, and claim it's just an example of their code comparison
techniques. But on slide 15 of their presentation
(http://www.vangennip.nl/perens/SCOsource_Briefing_II.2.pdf), they
clearly claim that it's System V code. This suggests that SCO have
recognized their error, though they haven't yet had the decency to
apologize to the BSD community.
Greg
--
Finger grog at lemis.com for PGP public key
See complete headers for address and phone numbers
next prev parent reply other threads:[~2003-09-11 17:32 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 [this message]
2003-09-11 17:25 ` Greg Lehey
-- 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=20030911173232.GD946@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).