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 19:54:35 +0200 [thread overview]
Message-ID: <20080130175435.GA29368@does.not.exist> (raw)
In-Reply-To: <1201658555.24898.27.camel@dv>
On Tue, Jan 29, 2008 at 09:02:35PM -0500, Pavel Roskin wrote:
> On Wed, 2008-01-30 at 02:25 +0200, Adrian Bunk wrote:
>
> > > > 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.
>
> OK, I'll think about it.
>
> > > 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.
>
> Thanks for the detailed analysis!
>
> Anyway, as far as I know, copyright covers copying of works,
The GPL might only talk about distribution.
But copyright law is not restricted to copying of work.
IANAL, and I don't know abou the laws in other countries, but at least
in Germany modifications of a copyrighted work require the permission of
the copyright holder.
It's e.g. a not so uncommon problem that someone wants to modify a 30 or
80 years old building, and since the original contract with the
architect did not grant the owner of the building the rights to modify
it he needs to ask the architect (or the architect's heirs) who has the
(nontransferable) copyright on the building for the permission to modify
the building. [1]
> and dynamic
> linking never creates anything suitable for copying. The "derived work"
> stays in memory, just like it does when a proprietary program runs on
> top of the Linux kernel. Memory dumps might be illegal to distribute
> though.
Look at what Geert quoted in this thread as opinion of actual lawyers.
> I'm not a lawyer and the above is not a legal advice. I don't represent
> Free Software Foundation.
>
> Regards,
> Pavel Roskin
cu
Adrian
[1] The building must be above the threshold of originality for giving
the architect a copyright and there are other laws that might
force the copyright holder to allow some modifications.
--
"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
next prev parent reply other threads:[~2008-01-30 17:54 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
2008-01-30 2:02 ` Pavel Roskin
2008-01-30 11:24 ` Rusty Russell
2008-01-30 17:54 ` Adrian Bunk [this message]
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=20080130175435.GA29368@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