From: Jamie Lokier <jamie@shareable.org>
To: balrogg@gmail.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] why is kqemu closed?
Date: Tue, 11 Apr 2006 14:58:22 +0100 [thread overview]
Message-ID: <20060411135822.GA14821@mail.shareable.org> (raw)
In-Reply-To: <fb249edb0604110533p25992db1j87f49848b11ef9d@mail.gmail.com>
andrzej zaborowski wrote:
> Anything released to the public by anyone is legal as long as it
> doesn't include (in it's content) parts of other people's
> copyrighted work. In this sense, kqemu can import whatever symbols
> it wants and have whatever license tag because when you download
> kqemu you're not downloading any piece of kernel's code as a part of
> kqemu.
That point is not correct.
Look up the legal terms "indirect infringement" and "contributory
infringement".
If an author distributes something whose principal use will be to
facilitate copyright infringement (i.e. by the users), then the author
may be found guilty of indirect infringement.
Both indirect infringement of GPL'd code, by distributing module
source code which depends on overly-intimate details of the kernel to
be useful, and direct infringement, by virtue of distributing compiled
binaries which use long inline definitions from kernel header files,
are among the theories about what may or may not be infringing. The
specially-marked symbols in Linux kernel source are guidelines and
indications of intention, which may prove relevant in a court of law
if judgement is required on a borderline case.
Note that I'm not saying anything about kqemu. Only pointing out that
it's false to say that distributing code you wrote yourself is never
copyright infringement.
> Now, whether using kqemu together with a linux kernel will still be
> legal is a different issue, but here the question is whether the user
> is breaking the law, not the author.
The GPL doesn't restrict linking and using whatever combination you
like. It only restricts distribution, which the user in your example
isn't doing. So end users are unlikely to be deemed guilty of anything.
-- Jamie
next prev parent reply other threads:[~2006-04-14 0:36 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-10 15:16 [Qemu-devel] why is kqemu closed? Rakotomandimby Mihamina
2006-04-10 15:20 ` Hetz Ben Hamo
2006-04-10 15:47 ` Auke Kok
2006-04-10 15:55 ` Hetz Ben Hamo
2006-04-10 15:56 ` Leonardo E. Reiter
2006-04-11 4:37 ` Auke Kok
2006-04-11 7:58 ` Brad Campbell
2006-04-11 16:22 ` Jim C. Brown
2006-04-11 8:37 ` Ricardo Almeida
2006-04-11 9:46 ` Johannes Schindelin
2006-04-11 10:05 ` Jamie Lokier
2006-04-11 15:05 ` Leonardo E. Reiter
2006-04-11 15:14 ` Jonas Maebe
2006-04-11 15:25 ` Jim C. Brown
2006-04-11 16:04 ` Jonas Maebe
2006-04-11 15:36 ` Paul Brook
2006-04-11 15:43 ` M. Warner Losh
2006-04-11 16:00 ` Paul Brook
2006-04-11 16:29 ` M. Warner Losh
2006-04-11 16:09 ` Jim C. Brown
2006-04-11 17:10 ` Enough already! " Bakul Shah
2006-04-11 15:17 ` Sebastian Kaliszewski
2006-04-11 15:31 ` M. Warner Losh
2006-04-11 12:33 ` andrzej zaborowski
2006-04-11 13:58 ` Jamie Lokier [this message]
2006-04-11 15:10 ` Sebastian Kaliszewski
2006-04-11 15:19 ` M. Warner Losh
2006-04-10 15:57 ` Brett (Mare) Henley
2006-04-10 16:02 ` Leonardo E. Reiter
2006-04-10 19:11 ` M. Warner Losh
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=20060411135822.GA14821@mail.shareable.org \
--to=jamie@shareable.org \
--cc=balrogg@gmail.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).