From: Balram Adlakha <b_adlakha@softhome.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Did the SCO Group plant UnixWare source in the Linux kernel?
Date: Fri, 2 May 2003 20:30:04 +0530 [thread overview]
Message-ID: <20030502150004.GA2048@localhost.localdomain> (raw)
In-Reply-To: <20030502140602.GH543@phunnypharm.org>
[-- Attachment #1: Type: text/plain, Size: 1539 bytes --]
On Fri, May 02, 2003 at 10:06:03AM -0400, Ben Collins wrote:
> > "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."
>
> This almost sounds like they are pointing to userspace code rather than
> kernel code. I know Redhat and other dists put patches on their kernels,
> but I seriously doubt it's anything like retrofiting UnixWare code. It's
> more like supporting newer hardware, performance tweaking, and such.
>
> --
> Debian - http://www.debian.org/
> Linux 1394 - http://www.linux1394.org/
> Subversion - http://subversion.tigris.org/
> Deqo - http://www.deqo.com/
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
They are pointing to nothing. They do not know themselves what they are
talking about. SCO is dead now, they have nothing else to do except for
framing other projects. If this thing was true they could have just
pointed out where exactly the stolen code was.
--
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-05-02 14:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-02 14:06 Did the SCO Group plant UnixWare source in the Linux kernel? Ben Collins
2003-05-02 15:00 ` Balram Adlakha [this message]
2003-05-02 15:11 ` Richard B. Johnson
-- strict thread matches above, loose matches on Subject: below --
2003-05-02 15:23 Downing, Thomas
2003-05-02 14:57 Downing, Thomas
2003-05-02 15:14 ` Richard B. Johnson
[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 3:21 The Spirit of Open Source
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
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=20030502150004.GA2048@localhost.localdomain \
--to=b_adlakha@softhome.net \
--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