From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1G7IRa-0007eb-E2 for qemu-devel@nongnu.org; Sun, 30 Jul 2006 17:03:26 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1G7IRZ-0007bW-2s for qemu-devel@nongnu.org; Sun, 30 Jul 2006 17:03:26 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1G7IRY-0007bH-Sl for qemu-devel@nongnu.org; Sun, 30 Jul 2006 17:03:24 -0400 Received: from [64.233.166.179] (helo=py-out-1112.google.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1G7IU4-00065q-PH for qemu-devel@nongnu.org; Sun, 30 Jul 2006 17:06:00 -0400 Received: by py-out-1112.google.com with SMTP id d42so416485pyd for ; Sun, 30 Jul 2006 14:02:48 -0700 (PDT) Message-ID: <2ad73a0607301402s7934f0e2ve30ab67989519f1@mail.gmail.com> Date: Sun, 30 Jul 2006 18:02:45 -0300 From: "=?ISO-8859-1?Q?Andr=E9_Braga?=" Subject: Re: [Qemu-devel] Re: Accelerator feature In-Reply-To: <20060730191139.85731.qmail@web27509.mail.ukl.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <8a6cde920607301143t2385ffa8od0b376abd6124b44@mail.gmail.com> <20060730191139.85731.qmail@web27509.mail.ukl.yahoo.com> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On 7/30/06, Karlos . wrote: > I asked lot of times before my first email why its closed. Dont assume that > i didnt it. Look, I'm subscribed to this list for more than two years now (since at least 18/July/2004), and I've never seen a SINGLE message from you. Fabrice already said he'd gladly open up the source for KQEMU IF, and ONLY IF, some company would provide him solid funding. He's trying to make a living there, you know? People who were uncomfortable with the closed source status of KQEMU then wrote qvm86. You don't like KQEMU's closed status? Then use qvm86. It's that simple. The source is closed because he so saw fit. It's his code, he CAN do it. And it's been obviously reverse-engineered by anyone able to run strace and objdump. (p.s.: I'm not by any means implying that the qvm86 authors reverse-engineered the closed part of KQEMU to derive qvm86's code. I meant that anyone with some skill could have reverse-engineered KQEMU enough [since it's so small] to check for any rogue/suspicious activities).