From: The Spirit of Open Source <tsoos@scoloses.org>
To: linux-kernel@vger.kernel.org
Subject: Did the SCO Group plant UnixWare source in the Linux kernel?
Date: 2 May 2003 03:21:36 -0000 [thread overview]
Message-ID: <ZIA7D8S737743.2233333333@Gilgamesh-frog.org> (raw)
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:
http://msnbc-cnet.com.com/2100-1016_3-999371.html
I can see a Linux developer copying copy from one of BSDs (which is cool), but
UnixWare?!? Come on.
If there's UnixWare source in the Linux kernel, a SCO Group employee put it
there! After all, who else would have such easy access to UnixWare sources?
If a SCO Group employee put the UnixWare source code into Linux, that begs the
question:
Did the SCO Group conspire to plant copyrighted code in the Linux
kernel so they could sue IBM for US$1 billion?
I believe the Justice Department calls that fraud, and that's a crime that CEOs
go to jail for. Are you listening Darl McBride?
next reply other threads:[~2003-05-02 3:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-02 3:21 The Spirit of Open Source [this message]
2003-05-02 4:28 ` Chris Friesen
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
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=ZIA7D8S737743.2233333333@Gilgamesh-frog.org \
--to=tsoos@scoloses.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®