qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Herbert Poetzl <herbert@13thfloor.at>
To: Grzegorz Kulewski <kangur@polcom.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] FreeOSZoo will stop March 1, 2005
Date: Thu, 17 Feb 2005 22:53:50 +0100	[thread overview]
Message-ID: <20050217215350.GB1446@mail.13thfloor.at> (raw)
In-Reply-To: <Pine.LNX.4.61.0502122308350.5918@alpha.polcom.net>

On Sat, Feb 12, 2005 at 11:41:55PM +0100, Grzegorz Kulewski wrote:
> Hi,
> 
> On Sat, 12 Feb 2005, Jean-Michel POURE wrote:
> >Following Fabrice decision to transform QEMU into a proprietary closed
> >solution
> 
> No, Fabrice did not transform QEMU into anything. He simply added another 
> optional module than can make QEMU faster and more bug-free. You can still 
> use QEMU without the accelerator and be perfectly happy with it. Also any 
> further development in area of IO, devices and so on will make both 
> versions better. KQEMU is only very small accelerator.

well, unfortunately together with the following mail ...

| From: Fabrice Bellard <fabrice@bellard.org>
| To: qemu-devel@nongnu.org
| Date: Sat, 29 Jan 2005 22:48:24 +0100
|
| Hi,
|
| I plan to remove the 'qemu-fast' target in the next release of QEMU. It
| is too painful to maintain, difficult to port and it needs a patched
| guest OS to work correctly.
|
| This target is replaced by the standard QEMU with soft mmu support. The
| QEMU Kernel Acceleration Layer which will be unveiled very soon will
| give much more performance while working with unpatched guest OSes.
|
| Fabrice.

the future looks more like this:

 - you want the same performance or better as before?
   then you have to use 'my' proprietary kernel module
   which isn't even open source (so that somebody
   could verify that it isn't that evil ...)

 - of course, you can use the slow version and
   contribute to the development of the commercial?
   version ...

> Think about PHP and different accelerators. PHP itself is free product 
> (PHP licence, IIRC). But there are many (often commercial but not all) 
> accelerators for it (one even made by Zend - autor of PHP). But this 
> does not make PHP less free. There are milions of people using PHP without 
> any accelerator, there are some using it with commercial accelerator and 
> there are few using it with one of free accelerators. Exactly the same 
> goes for QEMU.
> 
> QEMU is even better because no non-free part is linked with any code in 
> QEMU (userspace). This way no QEMU based free products (for example GUIs 
> or anything other) are affected by this addition and no licence is broken. 
> GPL, of course, allows calling non-free program or using GPLed program on 
> OS with non-free module.
> 
> Strictly speaking there are more problems at the kernel level. This is 
> because Linus and other gave their permission to load non-free modules to 
> the kernel but only as a special exception and mainly because some kernel 
> modules were written for some other OSes and were ported to Linux and 
> their code cannot be opened. This is not the case for KQEMU because it was 
> written especially for Linux but I think this is still more-or-less ok. 
> Nobody will hopefully complain.

proprietary kernel modules are a dangerous thing ...

 - first, you basically lose any support from the 
   kernel developers, when your kernel is tainted
 - then you do not know what the module will do to
   your system (i.e. what crashes it may cause)
 - and finally, if you're paranoid, you will not
   know what kind of information that module might
   gather and send to who-knows-where ...

> [ Fabrice, please make sure that all files linked with QEMU are free 
> because GPL demands that. I did not investigated this but if the header 
> for the module is used in userspace please make it free (BSD?) too. 
> Thanks. ]
> 
> Of course it will be better if KQEMU will go opensource but I hope it will 
> happen fast.

open source, good -- free software, even better ...

but don't get me wrong, it's totally up to Fabrice
under what license he releases his software, and
we have everything required to start of our own QEMU
branch (just under a different name if I got the 
Trademark comment right ;) and continue with free
software development based on qemu/qemu-fast ...

> >without any kind of future, I don't find any reason to loose my
> >company time and money fostering FreeOSZoo.
> 
> Of course its your decision and you have perfect right to make it. But 
> please think once more about it. I think that your project is very 
> valuable for the community.
> 
> 
> >I will hand over the project to any interested person, for exampe Raphaël 
> >if
> >he is interested by FreeOsZoo.
> 
> How fast must be the connection for it? How large is it? How much GB/month 
> does it generate currently?

I'm still hoping for the best, but expecting the
worst ... 

best,
Herbert

> Thanks,
> 
> Grzegorz Kulewski

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

  reply	other threads:[~2005-02-17 22:21 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
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 [this message]
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=20050217215350.GB1446@mail.13thfloor.at \
    --to=herbert@13thfloor.at \
    --cc=kangur@polcom.net \
    --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).