From: Paul Sokolovsky <pmiscml@gmail.com>
To: Rob Landley <rob@landley.net>
Cc: qemu-devel@nongnu.org
Subject: Re[2]: [Qemu-devel] Config file support
Date: Wed, 25 Oct 2006 03:18:31 +0300 [thread overview]
Message-ID: <557987790.20061025031831@gmail.com> (raw)
In-Reply-To: <200610241928.47477.rob@landley.net>
Hello Rob,
Wednesday, October 25, 2006, 2:28:47 AM, you wrote:
> On Monday 23 October 2006 9:38 pm, Paul Sokolovsky wrote:
>> Maybe. But where are new chips in qemu? Why there're still only 2
>> ARM boards? How do I "stick" wi-fi card in one of them? So the concern
>> is not just if it's easy to add new devices or not, but if there're means
>> to actually support appearance and growth of device library. Plugin system
>> would be a "decree" that there's a stable API to define devices and
>> welcome for 3rd-party developers to develop them.
> Because the lack of a stable internal API has completely prevented Linux from
> getting any sort of device support. It runs on far less hardware than things
> like Solaris, with such a stable API...
Oh, c'mon, Rob! I really didn't want to ask Paul Brook that, but
sure you'll fix my cluelessness right here, right now - tell me, tell me,
why Linux has dynamic-loadable modules support, which clueless passers-by
like me call "plugins"? It must be closed-source diversion, no? Those Linux
guys should really take that GPLv3 pill, don't you think? Yummy! ;-)
>> P.S. This is not a troll
> People who are not trolling generally don't have to _say_ they aren't
> trolling.
Well, let's face it - that's your comments on *.PIF files and XML
parsers that add spice (*1) to the discussion. So don't be surprised
that people start to reassure... ;-)
Oh, and while we still talking (and to add even more confusion),
how'd you guys managed to kill "ps ax" to work in busybox 1.2.1? I
really miss it here, when loading my embedded images into QEMU...
> Rob
*1 flamy
--
Best regards,
Paul mailto:pmiscml@gmail.com
next prev parent reply other threads:[~2006-10-25 0:18 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-20 17:55 [Qemu-devel] Config file support Chuck Brazie
2006-10-21 0:12 ` Johannes Schindelin
2006-10-21 10:00 ` Ricardo Almeida
2006-10-21 11:40 ` Stefan Weil
2006-10-22 9:51 ` Johannes Schindelin
2006-10-22 17:01 ` Flavio Visentin
2006-10-22 17:19 ` Martin Guy
2006-10-22 18:27 ` Paul Brook
2006-10-23 6:33 ` [Qemu-devel] " Antti P Miettinen
2006-10-23 20:01 ` [Qemu-devel] " Rob Landley
2006-10-23 20:29 ` Paul Brook
2006-10-23 22:22 ` Rob Landley
2006-10-23 23:33 ` Paul Brook
2006-10-24 9:04 ` Rob Landley
2006-10-24 10:47 ` Flavio Visentin
2006-10-24 12:05 ` Christian MICHON
2006-10-24 16:46 ` Blue Swirl
2006-10-24 20:38 ` Christian MICHON
2006-10-24 23:32 ` Rob Landley
2006-10-25 8:20 ` Johannes Schindelin
2006-10-24 0:11 ` andrzej zaborowski
2006-10-24 0:34 ` Paul Brook
2006-10-24 0:12 ` Re[2]: " Paul Sokolovsky
2006-10-24 0:36 ` Paul Brook
2006-10-24 1:38 ` Re[2]: " Paul Sokolovsky
2006-10-24 2:31 ` Paul Brook
2006-10-24 8:37 ` Christian MICHON
2006-10-24 23:28 ` Rob Landley
2006-10-25 0:18 ` Paul Sokolovsky [this message]
2006-10-25 15:01 ` Paul Brook
2006-10-26 14:31 ` Rob Landley
2006-10-27 20:00 ` Re[2]: " Paul Sokolovsky
2006-10-27 19:33 ` Paul Sokolovsky
2006-10-28 0:08 ` Paul Brook
2006-10-28 1:46 ` Re[2]: " Paul Sokolovsky
[not found] ` <20061025153503.GB5673@aon.at>
2006-10-28 22:24 ` busybox "ps ax" woes, was: " Paul Sokolovsky
2006-10-24 23:28 ` Rob Landley
2006-10-21 18:00 ` David Baird
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=557987790.20061025031831@gmail.com \
--to=pmiscml@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=rob@landley.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.