qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Jim C. Brown" <jma5@umd.edu>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] FreeOSZoo will stop March 1, 2005
Date: Sun, 13 Feb 2005 11:53:56 -0500	[thread overview]
Message-ID: <20050213165356.GA28580@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <420EF1E8.70603@mastros.biz>

On Sun, Feb 13, 2005 at 07:21:28AM +0100, James Mastros wrote:
> Jim C. Brown wrote:
> >>a) iEmulator wouldn't use kqemu anyway.  kqemu is for running 
> >>x86-on-x86.  iEmulator is for x86-on-PowerPC.  Thus, the iEmulator 
> >>people aren't loosing anything.
> >But they are using qemu. If qemu was closed source, then iEmulator 
> >wouldn't have
> >been able to do that.
> Yes, this is my point.  By making kqemu closed source, he isn't hurting 
> iEmulator, but is hurting people who do use it.

Irrevevant. If qemu was closed source from the start, iEmulator wouldn't
have been able to do anything period (short of massive disassembly &
re-engineering).

>  The iEmulator people 
> couldn't care less about the status of kqemu.  Sure, it may have a bad 
> effect on some other people selling qemu wrappers.  It certainly has ill 
> effects on people who are trying to run x86-on-x86, and having problems, 
> because they can't try looking through the kqemu source, and fixing 
> problems that may live there.

Say kqemu was made open source, and say that iEmulator decided to expand by
releasing a new product, kVirtual. They could do this all over again, and
make more profit. Or maybe some other company unrelated to iEmulator could
use kqemu to make kVirtual.

The point I was making is that maybe Fabrice can't do anything about them
now, but he at least wants to avoid a repeat.

> 
> >Of course qemu isnt under the GPL at all, so that is impossible. Only 
> >qemu-user
> >code uses the GPL license, and that is probably due to the fact that it 
> >uses
> >linux kernel code.
> Yes, it is, read LICENSE.  qemu-user is under the GPL (proper), 
> qemu-proper and libqemu are under the lesser GPL. 

GPL != LGPL

The main difference being, LGPL makes what iEmulator is doing perfectly legal
as they don't need to give the source code unless they modify the qemu code.

Since it is LGPL & they give Fabric credit, iEmulator has done nothing illegal.

> I'd recommend to 
> Fabrice re-licensing under the GPL proper instead of the LGPL -- if you 
> don't like people selling products based on qemu without them being 
> open-source, then the GPL is probably closer to your wishes then the 
> LGPL.

I agree.

> 
> >>If iEmulator is not breaking the GPL, then put the code into the qemu 
> >>CVS.  If they are, then start making quiet threats.  If they don't open 
> >>up, then talk to GNU, http://www.softwarefreedom.org/.  If they still 
> >>don't, then it's time to make loud threats -- post to /., etc.
> >>
> >>Don't punish everybody because a few folks aren't playing by the rules.
> >
> >I agree, but the main problem would be legal. If you can't get the courts
> >to side with you, then you're sunk.
> Well, that's really not true.  The main problem is economic.  If you 
> make it uneconomical for the "bad" people to behave the way they are, 
> they will stop.  You can do that by going through the courts, and 
> obtaining a judgment, but that's quite possibly worse for you then it is 
> for them -- even if you win.

Exactly.

> 
> You can also go to the court of public opinion.  How many of iEmulator's 
> customers read /.?  How many would still be customers if they found out 
> that iEmulator rips off open-source code, which they could just as well 
> use directly, and not pay thirty bucks for, to boot?  I suspect enough 
> of them that they will want to comply with the license, and avoid 
> embaressment.

I didn't think of that.

Of course, how many VMware users read slashdot? How many coperate execs?
How many Windows users?

This approach could work (and imnsho it is worth the risk) but Fabrice might
want something more substantial. At this point I've gone beyond second guessing
tho.

> 
> >Presumably he's going to sell kqemu, and he is using this as a test run 
> >before
> >he tries to sell the code to the big companies and get the megabucks. (At 
> >least
> >that is what I would do.)
> That's a possibility.  If that's true, then I hope the company that buys 
> him out is very nice, or we're all going to be out a maintainer of an 
> open source system emulator rather soon.  I'd much rather that he sell 
> out to the collective of his users rather then to some faceless 
> corporate overlord who will make us all use a vmware clone, rather then 
> an open source project I've become somewhat fond of.

Agreed.

> 
> 	-=- James Mastros
> 
> 
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
> 

-- 
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.

  parent reply	other threads:[~2005-02-13 17:24 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-12  9:18 [Qemu-devel] FreeOSZoo will stop March 1, 2005 Jean-Michel POURE
2005-02-12 10:15 ` Magnus Damm
2005-02-12 10:18 ` Brad Campbell
2005-02-12 12:19   ` Antti-Juhani Kaijanaho
2005-02-12 12:20   ` Daniel Egger
2005-02-12 13:42     ` Brad Campbell
2005-02-12 16:15       ` Daniel Egger
2005-02-12 17:00         ` Fabrice Bellard
2005-02-12 18:11         ` Jernej Simončič
2005-02-12 21:18           ` Daniel Egger
2005-02-12 23:01             ` Darrin Ritter
2005-02-13  0:06             ` Jernej Simončič
2005-02-13 11:28               ` Daniel Egger
2005-02-13 17:01                 ` Jim C. Brown
2005-02-13 17:40                   ` [Qemu-devel] Plex86 and Qemu jeebs
2005-02-13 18:27                     ` Jim C. Brown
2005-02-13 19:35                       ` jeebs
2005-02-13 22:06                         ` Jim C. Brown
2005-02-13 23:20                           ` jeebs
2005-02-14  0:05                             ` [Qemu-devel] coLinux and Qemu? --was-- " Darryl Dixon
2005-02-14  0:37                               ` Jim C. Brown
2005-02-14  0:58                                 ` Mark Williamson
2005-02-14  0:34                             ` [Qemu-devel] " Jim C. Brown
2005-02-14 10:39                           ` Andreas Bollhalder
2005-02-13 22:18                         ` Adrian Smarzewski
2005-02-13 23:04                           ` Martin Koniczek
2005-02-14 14:18                         ` Phil Krylov
2005-02-15 23:32               ` Old version support. Was: Re: [Qemu-devel] FreeOSZoo will stop March 1, 2005 Gregory Alexander
2005-02-16 18:51                 ` Fabrice Bellard
2005-02-13  0:18   ` Jim C. Brown
2005-02-13  4:42     ` James Mastros
2005-02-13  5:26       ` Jim C. Brown
2005-02-13  6:21         ` James Mastros
2005-02-13 10:02           ` Darryl Dixon
2005-02-13 16:53           ` Jim C. Brown [this message]
2005-02-13 13:32     ` [Qemu-devel] " Robert Wittams
2005-02-12 22:41 ` [Qemu-devel] " Grzegorz Kulewski
2005-02-17 21:53   ` Herbert Poetzl
2005-02-17 22:18     ` Grzegorz Kulewski
2005-02-17 23:25       ` Fabrice Bellard
2005-02-18  4:29         ` John R. Hogerhuis
2005-02-18  8:23           ` Asko Kauppi
2005-02-18 11:05           ` Elefterios Stamatogiannakis

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=20050213165356.GA28580@jbrown.mylinuxbox.org \
    --to=jma5@umd.edu \
    --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).