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 19:22:05 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0706221907490.4059@racer.site> (raw)
In-Reply-To: <200706221300.32644.luke@dashjr.org>

Hi,

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

> On Friday 22 June 2007 12:37, Johannes Schindelin wrote:
> > 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.
> 
> Not if you want to distribute the GPL'd work, or anything derived from it.

You can distribute on the same medium, at the same time, two different 
programs, one GPL, the other not. No problem. None at all.

> > The GPL is only insofar viral as you cannot take something GPLed and 
> > just relicense it at will. Not even when you modify it.
> 
> Then explain the difference between the LGPL and GPL. A license that 
> preserves itself only is pointless without other terms.

No, it is not.

> > 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.
> 
> That allows you to distribute the virtual device by itself, not 
> alongside with Qemu.

To the contrary. You can distribute them both at the same time, under 
different conditions, much like you can distribute QEmu with parts GPL, 
parts LGPL, and parts BSD.

> > Besides, QEmu's core is LGPL. Not GPL.
> 
> Good point, and makes this entire argument mostly irrelevant.

Not at all. If it was a derivative work of the LGPLed part, it would still 
have to be LGPLed.

> > > It is undisputed that it would be in violation if the kernel was 
> > > distributed with the modules.
> >
> > Nope. It is not undisputed.
> 
> It is undisputed by anyone who has ever considered the issue as part of 
> deciding whether or not to do it.

There are distributions which deliver closed source binary-only modules. 
Many LiveCDs for example.

> > > 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.
> 
> http://www.kroah.com/log/linux/ols_2006_keynote.html

That is Greg's opinion. There are others. Notably Linus'.

> > 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.
> 
> I would never buy software without source. Hopefully someday I can apply 
> this to hardware as well.

That is your freedom.

Frankly, I get really bored by the license discussions these days. Gone 
seem the days where you discussed code and algorithms on the mailing 
lists. Sigh.

Ciao,
Dscho

  reply	other threads:[~2007-06-22 18:22 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
2007-06-22 18:00                 ` Luke -Jr
2007-06-22 18:22                   ` Johannes Schindelin [this message]
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.0706221907490.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).