public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Chris Abbey <linux@cabbey.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: possible GPL violation involving linux kernel code
Date: Sun, 21 Apr 2002 07:48:58 +0100	[thread overview]
Message-ID: <20020421074858.A8318@infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0204200024030.24652-100000@tweedle.cabbey.net>

On Sun, Apr 21, 2002 at 01:43:58AM -0500, Chris Abbey wrote:
> I just know I'm going to regret posting this, but I can think of
> no better group to notify of this than the copyright holders, and
> no better location for the majority of them then l-k.
> 
> While searching through all of the driver images on Promise Tech's
> website I stumbled across their disk images for Caldera/Open Linux
> and their TX2 card ( http://promise.com/support/file/ftol_12014.tgz )
> 
> This tarball contains two disk images:
> -rw-r--r--    1 cabbey    1474560 Nov 19 01:29 ols31-ft.img
> -rw-r--r--    1 cabbey    1474560 Nov 19 01:27 olw31-ft.img
> 
> which in turn contain binary modules from 2.4.2 and 2.4.3
> (intermixed, I found some modules from 2.4.2 and some from
> 2.4.3, as well as a few of their rc's)
> 
> The contents of one of these images (ols31-ft.img) is as such
> (ther other disk is very similar):

Calm down - OpenLinux driver disks are supposed to contain the standard
modules in addition to the new ones.  You can find your sources in
/usr/src/linux.


  reply	other threads:[~2002-04-21  6:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-21  6:43 possible GPL violation involving linux kernel code Chris Abbey
2002-04-21  6:48 ` Christoph Hellwig [this message]
2002-04-21  6:52   ` Chris Abbey
2002-04-21 11:17     ` Christoph Hellwig
2002-04-21 14:10       ` Eric W. Biederman
2002-04-22 18:42         ` Doug Ledford
2002-04-21 20:14       ` Chris Abbey
2002-04-21 20:54         ` Sean Neakums
2002-04-22  0:05       ` Pavel Machek
2002-04-21 17:27 ` Sean Neakums

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=20020421074858.A8318@infradead.org \
    --to=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@cabbey.net \
    /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