From: "andrzej zaborowski" <balrog@zabor.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] why is kqemu closed?
Date: Tue, 11 Apr 2006 14:33:46 +0200 [thread overview]
Message-ID: <fb249edb0604110533p25992db1j87f49848b11ef9d@mail.gmail.com> (raw)
In-Reply-To: <443A8033.9000409@win4lin.com>
On 10/04/06, Leonardo E. Reiter <lreiter@win4lin.com> wrote:
> No it's not! In fact, in the latest version, he explicitly gives it a
> commercial ("Proprietary") license. He also does not import any
> exported GPL symbols from the kernel. In fact, if your claim is true,
Legally, even without the "Propriotary" tag, or even importing some
GPL symbols from the kernel, kqemu is still absolutely valid. 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.
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.
> then the following very popular products violate the kernel license
> agreement:
>
> VMware Workstation, GSX Server, ESX Server, Server Beta (free)
> Parallels Workstation
> NVIDIA drivers
> Win4Lin 9x (shameless self-promotion, I admit)
> Win4Lin Pro (which distributes KQEMU under license from Fabrice)
>
> In fact, KQEMU uses almost no kernel functionality at all. Allocating,
> freeing, and locking memory into place is not that interesting and is
> not something that Linux does alone - every OS in existence provides
> these services. On Linux, you are not forced to be a GPL module to use
> them, because, they are simply not that interesting and are mandatory to
> run just about any type of application or driver. The real meat of
> KQEMU is kernel-independent (the same binary runs on just about any OS,
> unmodified), and deals with the CPU directly. It would be a crying
> shame if drivers like these would not be allowed in future kernels -
> they use the kernel as simply a loader, not to do anything really
> interesting.
>
> I admit since I am a vendor, I have certain biases against forcing all
> software to be GPL. However I respect these licenses fully, and also
> respect the author's choice to use whatever license he or she pleases,
> and also to allow exceptions to these licenses. You might recall Linus
> Torvalds years ago explicitly giving an exception to "binding" when it
> came to loading kernel modules. It would be hard to convince any vendor
> in the world to develop software for Linux if you were not allowed to
> run non-GPL applications on Linux. Let's hope that never happens,
> although I understand that the latest sentiments seem to unfortunately
> be leaning that way. This is not how Linux will beat Windows on the
> desktop, nor on the server!
>
> Regards,
>
> Leo Reiter
>
> Auke Kok wrote:
> >
> > On Mon, 10 Apr 2006 17:20:54 +0200, "Hetz Ben Hamo" <hetzbh@gmail.com> wrote:
> >
> >>Fabrice is the owner of the KQEMU code, and he decides for his own
> >>reasons to put the code under closed source license.
> >
> >
> > I'm sure that Fabrice knows and that I'm beating a dead horse, but this is (strictly speaking, discussions pending ;^)) violating the linux kernel license agreement.
> >
> > Auke
> >
> >
> >
> > _______________________________________________
> > Qemu-devel mailing list
> > Qemu-devel@nongnu.org
> > http://lists.nongnu.org/mailman/listinfo/qemu-devel
>
> --
> Leonardo E. Reiter
> Vice President of Product Development, CTO
>
> Win4Lin, Inc.
> Virtual Computing from Desktop to Data Center
> Main: +1 512 339 7979
> Fax: +1 512 532 6501
> http://www.win4lin.com
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>
Regards,
Andrew
--
balrog 2oo6
Dear Outlook users: Please remove me from your address books
http://www.newsforge.com/article.pl?sid=03/08/21/143258
next prev parent reply other threads:[~2006-04-11 12:33 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 [this message]
2006-04-11 13:58 ` Jamie Lokier
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=fb249edb0604110533p25992db1j87f49848b11ef9d@mail.gmail.com \
--to=balrog@zabor.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).