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 00:26:29 -0500 [thread overview]
Message-ID: <20050213052629.GA23176@jbrown.mylinuxbox.org> (raw)
In-Reply-To: <420EDABF.1090203@mastros.biz>
On Sun, Feb 13, 2005 at 05:42:39AM +0100, James Mastros wrote:
> Jim C. Brown wrote:
> >1) There are those that use qemu without giving Fabrice any money or credit
> >(such as iEmulator). This is best resolved by legal action, but it may be
> >difficult for a single person to fight against an entire company,
> >financial-wise.
> If this is the reason, and I think it is part of it, then it is a bad
> reason.
>
> 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.
>
> b) A far more effective way would be to first verify that they are
> actually breaking the GPL -- when you purchase iEmulator, do they give
> you a copy of the qemu source with it? Are you given all rights to the
> qemu source you get as you would under the GPL? Do they link code
> licensed GPL-incompatabiliy with qemu code?
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.
qemu system emulation is under the BSD license iirc.
>
> 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.
>
> >2) Fabrice wants to hold on to the source in order to make revenue from it
> >in
> >the future.
> This is really a much more reasonable position, but if this is his
> position, he should probably state what it would take to open the
> current source for kqemu, and set up a way to take donations for the
> fund. If he gets to his target, then do it again when he's ready to
> make the next big leap forward -- assuming, that is, that it isn't based
> upon GPL code from other parties. (There's nothing illegal about basing
> it on your own GPL'd code.)
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.)
>
> Since he hasn't responded to any of the several attempts to give him
> money, I rather doubt money is his primary concern, but rather respect
> and credit, which I can certainly understand -- but making kqemu
> closed-source isn't a good way to cause this to happen.
>
> Despite this, I will probably be making several code contributions to
> qemu in the nearish future. (PC speaker support, and possibly faster
> graphics code.) I probably won't be contributing money, as it's rather
> tight for me -- sorry, Fabrice.
>
> -=- James Mastros
>
--
Infinite complexity begets infinite beauty.
Infinite precision begets infinite perfection.
next prev parent reply other threads:[~2005-02-13 5:56 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 [this message]
2005-02-13 6:21 ` James Mastros
2005-02-13 10:02 ` Darryl Dixon
2005-02-13 16:53 ` Jim C. Brown
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=20050213052629.GA23176@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).