From: Doug Ledford <dledford@redhat.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Chris Abbey <linux@cabbey.net>,
linux-kernel@vger.kernel.org
Subject: Re: possible GPL violation involving linux kernel code
Date: Mon, 22 Apr 2002 14:42:15 -0400 [thread overview]
Message-ID: <20020422144215.A877@redhat.com> (raw)
In-Reply-To: <20020421074858.A8318@infradead.org> <Pine.LNX.4.33.0204210147550.26531-100000@tweedle.cabbey.net> <20020421121732.A16765@infradead.org> <m11yd93zxg.fsf@frodo.biederman.org>
On Sun, Apr 21, 2002 at 08:10:35AM -0600, Eric W. Biederman wrote:
> Christoph Hellwig <hch@infradead.org> writes:
> > Where the heck did you get the impression from that this is required by
> > the GPL?
> >
> > Christoph
> GPL section 3
>
> 3. You may copy and distribute the Program (or a work based on it,
> under Section 2) in object code or executable form under the terms of
> Sections 1 and 2 above provided that you also do one of the following:
>
> a) Accompany it with the complete corresponding machine-readable
> source code, which must be distributed under the terms of Sections
> 1 and 2 above on a medium customarily used for software interchange; or,
And Cristoph's point is that Promise has already complied with this exact
section. The disk they distribute is a driver disk for Caldera Open
Linux. That disk format happens to require that they put the regular
kernel drivers from the standard install disk into an image and then
simply add their new driver to that image as well. That means you already
have all the GPL required source on the image you are installing because
all those kernel modules are bit for bit duplicates of the ones that came
with your open linux CD. End of problem.
--
Doug Ledford <dledford@redhat.com> 919-754-3700 x44233
Red Hat, Inc.
1801 Varsity Dr.
Raleigh, NC 27606
next prev parent reply other threads:[~2002-04-22 18:42 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
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 [this message]
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=20020422144215.A877@redhat.com \
--to=dledford@redhat.com \
--cc=ebiederm@xmission.com \
--cc=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