From: Chris Friesen <cfriesen@nortelnetworks.com>
To: The Spirit of Open Source <tsoos@scoloses.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Did the SCO Group plant UnixWare source in the Linux kernel?
Date: Fri, 02 May 2003 00:28:53 -0400 [thread overview]
Message-ID: <3EB1F405.3050000@nortelnetworks.com> (raw)
In-Reply-To: ZIA7D8S737743.2233333333@Gilgamesh-frog.org
The Spirit of Open Source wrote:
> This C|Net news article says the SCO Group claims to have found many instances
> of copyrighted UnixWare source code being inserted verbatim into the Linux
> kernel:
According to an article here:
http://slashdot.org/articles/03/05/01/2332226.shtml?tid=167&tid=99
SCO-Caldera Senior Vice President Chris Sontag explicitly says that the
kernel.org kernel is *not* tainted, but that that other stuff that Red Hat and
SuSE are including *is*.
Quote from the interview:
"Chris Sontag: We're not talking about the Linux kernel that Linus and others
have helped develop. We're talking about what's on the periphery of the Linux
kernel."
He doesn't specify exactly what he's talking about, but he makes an interesting
claim:
"Chris Sontag: We are using objective third parties to do comparisons of our
UNIX System V [SCO-owned Unix] source code and Red Hat as an example. We are
coming across many instances where our proprietary software has simply been
copied and pasted or changed in order to hide the origin of our System V code in
Red Hat. This is the kind of thing that we will need to address with many Linux
distribution companies at some point."
Chris
--
Chris Friesen | MailStop: 043/33/F10
Nortel Networks | work: (613) 765-0557
3500 Carling Avenue | fax: (613) 765-2986
Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
next prev parent reply other threads:[~2003-05-02 4:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-02 3:21 Did the SCO Group plant UnixWare source in the Linux kernel? The Spirit of Open Source
2003-05-02 4:28 ` Chris Friesen [this message]
2003-05-02 5:43 ` Christoph Hellwig
2003-05-02 12:57 ` jlnance
2003-05-03 2:10 ` jw schultz
2003-05-03 4:26 ` Daniel Phillips
2003-05-02 15:53 ` Carl-Daniel Hailfinger
2003-05-02 16:38 ` John Jasen
2003-05-02 17:20 ` Carl-Daniel Hailfinger
2003-05-02 17:28 ` John Jasen
2003-05-02 17:43 ` Carl-Daniel Hailfinger
[not found] <fa.gqa0utv.1i0gigr@ifi.uio.no>
2003-05-02 12:40 ` Nomen Nescio
2003-05-02 14:02 ` Chris Friesen
-- strict thread matches above, loose matches on Subject: below --
2003-05-02 14:06 Ben Collins
2003-05-02 15:00 ` Balram Adlakha
2003-05-02 15:11 ` Richard B. Johnson
2003-05-02 14:57 Downing, Thomas
2003-05-02 15:14 ` Richard B. Johnson
2003-05-02 15:23 Downing, Thomas
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=3EB1F405.3050000@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tsoos@scoloses.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