public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@kernel.org>
To: Pavel Roskin <proski@gnu.org>
Cc: linux-kernel@vger.kernel.org,
	Jon Masters <jonathan@jonmasters.org>,
	Rusty Russell <rusty@rustcorp.com.au>,
	Giridhar Pemmasani <pgiri@yahoo.com>,
	rms@gnu.org
Subject: Re: ndiswrapper and GPL-only symbols redux
Date: Wed, 30 Jan 2008 02:25:14 +0200	[thread overview]
Message-ID: <20080130002514.GA1802@does.not.exist> (raw)
In-Reply-To: <1201650267.18773.118.camel@dv>

On Tue, Jan 29, 2008 at 06:44:27PM -0500, Pavel Roskin wrote:
> On Wed, 2008-01-30 at 00:57 +0200, Adrian Bunk wrote:
> > On Tue, Jan 29, 2008 at 04:22:45PM -0500, Pavel Roskin wrote:
> > > Hello!
> > > 
> > > It have come to my attention that a patch has been committed to the
> > > kernel with the explicit purpose of tainting ndiswrapper - the kernel
> > > module allowing Windows NDIS drivers for Ethernet and Wireless cards to
> > > be used by the kernel.
> > >...
> > > Just to reiterate some points from the old discussion:
> > >...
> > > - no copyright violation is involved, as Windows drivers are not derived
> > > from Linux sources
> > >...
> > 
> > It is interesting that someone posting with an @gnu.org address claims
> > that dynamic linking of not GPLv2 compatible code into GPLv2 code was
> > not a copyright violation.
> 
> No, I'm representing myself only.  I don't think you represent all
> kernel developers when posting from the kernel.org address.

I'm not using my @kernel.org address except for kernel issues and I'm 
not using a company address in linux-kernel discussions.

Mailing lists of a project or a company are something completely 
different from using a project or company address outside of the 
project.

> I'm actually surprised that you are raising this issue.  If the
> motivation to ban ndiswrapper is based on the copyright law, doesn't it
> meant that we have DRM in the kernel now?  Is Linux going to enforce
> copyright laws across the world?
> 
> > Is it an official statement of the FSF that such linking is considered 
> > legal?
> 
> Absolutely not.
> 
> > (RMS added to Cc)
> 
> I, for one, would welcome an informed position of the FSF.  It may have
> interesting implications for Wine, ReactOS, mplayer, qemu, Java and many
> other programs loading non-free compiled code at the run time.

Wine is licenced under the terms of the LGPL.

ReactOS is licenced under the terms of the GPL with a licence 
exception for runtime linking of non-free modules.

QEMU is licenced under the terms of the GPL with a licence exception for 
runtime linking with libqemu.a.

GNU classpath (and libgcj) are licenced under the terms of the GPL with 
a licence exception for runtime linking with it.

As you can see, all of the above explicitely address this issue.

The only program from your list that has a fishy licencing is mplayer.

> Regards,
> Pavel Roskin

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2008-01-30  0:24 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-29 21:22 ndiswrapper and GPL-only symbols redux Pavel Roskin
2008-01-29 22:27 ` Valdis.Kletnieks
2008-01-29 22:35   ` Giridhar Pemmasani
2008-01-29 23:21   ` Pavel Roskin
2008-01-30  0:25     ` Jon Masters
2008-01-29 22:45 ` Alan Cox
2008-01-29 23:56   ` Pavel Roskin
2008-01-30  3:24     ` Andi Kleen
2008-01-30  5:07       ` Jon Masters
2008-01-30  5:26         ` Pavel Roskin
2008-01-30  6:03           ` Andi Kleen
2008-01-30  6:12             ` Pavel Roskin
2008-01-29 22:57 ` Adrian Bunk
2008-01-29 23:04   ` Alan Cox
2008-01-29 23:06   ` Jan Engelhardt
2008-01-29 23:25   ` Måns Rullgård
2008-01-30  0:35     ` Adrian Bunk
2008-01-30  0:46       ` Måns Rullgård
2008-01-30  1:44         ` Daniel Hazelton
2008-01-30  7:38         ` Geert Uytterhoeven
2008-01-30  8:45           ` Måns Rullgård
2008-01-30 21:00           ` David Schwartz
2008-01-29 23:44   ` Pavel Roskin
2008-01-30  0:25     ` Adrian Bunk [this message]
2008-01-30  2:02       ` Pavel Roskin
2008-01-30 11:24         ` Rusty Russell
2008-01-30 17:54         ` Adrian Bunk
2008-01-30 18:15           ` Lennart Sorensen
2008-01-30 18:45             ` Adrian Bunk
2008-01-30 19:43               ` Lennart Sorensen
2008-01-30 20:26                 ` Valdis.Kletnieks
2008-01-30 21:09                   ` Adrian Bunk
     [not found]     ` <E1JKJvh-0006P8-Pi@fencepost.gnu.org>
2008-02-01  5:08       ` Pavel Roskin
2008-02-06 10:50         ` Adrian Bunk
2008-02-06 11:11           ` Xavier Bestel
2008-02-06 11:38           ` David Schwartz
2008-02-06 15:10             ` Theodore Tso
2008-01-30  0:48   ` Giridhar Pemmasani
2008-01-30 17:54     ` Adrian Bunk
2008-01-30 18:26       ` Chris Friesen
2008-01-30 18:54         ` Adrian Bunk
2008-01-30 19:36           ` Lee Revell
2008-01-30 20:28             ` Adrian Bunk
2008-01-31  1:00               ` Michael Gerdau
2008-02-05 13:00                 ` Adrian Bunk
2008-02-04 12:42             ` Alan Cox
2008-02-04 13:56               ` Adrian Bunk
2008-01-31  3:25       ` David Newall
2008-01-31 15:20         ` Chris Friesen
2008-01-30  0:20 ` Jon Masters
2008-01-30  0:35   ` Jan Engelhardt
2008-01-30  0:48     ` Jon Masters
2008-01-30  1:33       ` Pavel Roskin
2008-01-30  1:48   ` Pavel Roskin
2008-01-30  2:08     ` Jan Engelhardt
2008-01-30  5:04     ` Jon Masters
2008-01-30  5:38       ` Zan Lynx
2008-01-30  7:40         ` Geert Uytterhoeven
2008-01-30  8:54           ` Måns Rullgård
2008-01-30 20:50       ` David Schwartz

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=20080130002514.GA1802@does.not.exist \
    --to=bunk@kernel.org \
    --cc=jonathan@jonmasters.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pgiri@yahoo.com \
    --cc=proski@gnu.org \
    --cc=rms@gnu.org \
    --cc=rusty@rustcorp.com.au \
    /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