qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Luke -Jr <luke@dashjr.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] QEMU License and proprietary hardware
Date: Fri, 22 Jun 2007 18:37:36 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0706221821210.4059@racer.site> (raw)
In-Reply-To: <200706221211.58845.luke@dashjr.org>

Hi,

On Fri, 22 Jun 2007, Luke -Jr wrote:

> On Friday 22 June 2007 11:46, M. Warner Losh wrote:
>
> > If what you did somehow wasn't a derivative work, then the there's no 
> > legal basis for forcing compliance with a license.
> 
> Unless you modify or distribute the work. These acts are illegal without 
> compliance with the license.

No. If what you did was not a derivative work, then it was no derivative 
work, then it was no derivative work.

So if you changed a GPL program, and distribute that, you have to license 
these changes with the same license.

If at the same time you make something original, which is not derived from 
the GPLed program, then you are as free as a bird to sh*t on the GPL with 
regards to your original work. You can choose whatever license, if any.

What you throw about here, Luke, is FUD.

The GPL is only insofar viral as you cannot take something GPLed and just 
relicense it at will. Not even when you modify it.

However, writing a virtual device that just happens to be dynamically 
linkable to QEmu, but might just as well be linked to VMWare, is fine. 
This virtual device is clearly _not_ derived from QEmu.

You can do something like that easily, by implementing a clean interface 
for QEmu, which allows you to runtime link with such a standalone virtual 
device. A couple of people would even thank you for that.

Besides, QEmu's core is LGPL. Not GPL.

All this discussion is moot though. If you're not a lawyer, you should 
not behave like one, and respect the wishes of the authors for a change.

> It is undisputed that it would be in violation if the kernel was 
> distributed with the modules.

Nope. It is not undisputed.

> The GPL is clear that mere use (end user) is always allowed.

That's right.

> It is also fairly clear (the opinions of many kernel developers and IP 
> lawyers) that proprietary modules for Linux are illegal to distribute.

Nope. Not at all.

I'd rather have your virtual device open sourced, but if you cannot do 
that, I'd rather have it closed-source, than not at all.

And please stop this FUD about the GPL being viral and stuff.

Ciao,
Dscho

  parent reply	other threads:[~2007-06-22 17:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-21 11:28 [Qemu-devel] QEMU License and proprietary hardware Armbrost Failsafe
2007-06-21 22:24 ` Luke -Jr
2007-06-21 22:33   ` M. Warner Losh
2007-06-22 15:18     ` Luke -Jr
2007-06-22 16:07       ` Warner Losh
2007-06-22 16:23         ` Luke -Jr
2007-06-22 16:46           ` M. Warner Losh
2007-06-22 17:11             ` Luke -Jr
2007-06-22 17:30               ` M. Warner Losh
2007-06-22 17:31               ` Ronnie Misra
2007-06-22 17:37               ` Johannes Schindelin [this message]
2007-06-22 18:00                 ` Luke -Jr
2007-06-22 18:22                   ` Johannes Schindelin
2007-06-24 20:10 ` Paul Brook
  -- strict thread matches above, loose matches on Subject: below --
2007-06-22  5:34 Balazs Attila-Mihaly (Cd-MaN)
2007-06-22 15:21 ` Luke -Jr

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=Pine.LNX.4.64.0706221821210.4059@racer.site \
    --to=johannes.schindelin@gmx.de \
    --cc=luke@dashjr.org \
    --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).