qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jamie Lokier <jamie@shareable.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] why is kqemu closed?
Date: Tue, 11 Apr 2006 11:05:37 +0100	[thread overview]
Message-ID: <20060411100536.GC27657@mail.shareable.org> (raw)
In-Reply-To: <Pine.LNX.4.63.0604111144220.21715@wbgn013.biozentrum.uni-wuerzburg.de>

Johannes Schindelin wrote:
> > I do not think that kqemu benefits from being closed source, and probably more
> > people with me. People will pick an open implementation before any closed one,
> > even industry, they're picking up faster than you think ;^)
> > 
> > I did not agree with kqemu being released without the proprietary flag, which
> > is why I submitted the issue, and,if I can help it, it'll be open source or
> > surpassed by something that is - no offense.
> 
> This is BS. You are basically going into a restaurant and say: "I don't 
> think that lovely steak benefits from having a price tag. I do not agree 
> with having to pay for this steak, and if I can help it, it'll be for 
> free."
> 
> Think about it. Fabrice does a wonderful job. Guess who's paying him.

Besides, there is already an open source equivalent to kqemu, called
kvm86, isn't there?  I'm surprised it doesn't get more attention.

Perhaps that indicates that people _don't_ pick the open
implementation before the closed one, when the author is respected as
much as Fabrice?

-- Jamie

  reply	other threads:[~2006-04-14  0:36 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 [this message]
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
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=20060411100536.GC27657@mail.shareable.org \
    --to=jamie@shareable.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).