From: Rudi Lippert <Rudi@LYRIKpage.de>
To: jhoger@pobox.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Qemu workstation
Date: Mon, 5 Apr 2004 11:30:00 +0200 [thread overview]
Message-ID: <200404051130.04164.Rudi@LYRIKpage.de> (raw)
In-Reply-To: <1081156203.3939.10.camel@aragorn>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
i agree. i don't know anything about the windows port, but personally, i think
the draft of the linux-frontend looks more functional.
one thing about multitasking: there should probably be an option in the
preferences dialog allowing to STOP the vm as soon as the focus goes to
another one and to CONT that one. that would definitely be a step ahead of
vmware, since they don't allow stopping a vm without dumping the memory to
the hd.
it is probably too early to talk about these things, but it came to my mind
today, so why not post it today.
another question: are there sources available for the linux frontend? many
people on this list will also test the frontend, which would certainly speed
up its development.
€0.06
"Re: [Qemu-devel] Qemu workstation" (John R. Hogerhuis, Monday 05 April 2004
11:10):
> Sweet Jesus... a new name, vmware shell look alike (not a step in the
> right direction IMHO... we could probably come up with a better UI than
> to rehash vmware's...) and the win32 port is not really operational yet
> (unless 0.5.3 actually made it process .iso files... I haven't built
> yet...)
>
> Well I guess there's something to be said for multi-tasking.
>
> Does anyone know who this is? I'd like to find out what kind of magic
> they are performing to get ReactOS running in win32 port.
>
> Alas I suspect GIMP at work...
>
> -- John.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFAcScc1nTg39QS/TsRAt72AJ4wGaL9c/iwA+a7R8dL5qznUZVf7ACeJtDs
v4GGCxmFBog9WbCrmLO7DHg=
=mdod
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-04-05 9:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-05 8:47 [Qemu-devel] Qemu workstation Jean-Michel POURE
2004-04-05 9:10 ` John R. Hogerhuis
2004-04-05 9:30 ` Rudi Lippert [this message]
2004-04-05 9:55 ` Jean-Michel POURE
2004-04-05 19:31 ` Fabrice Bellard
2004-04-05 21:49 ` Jamie Burns
2004-04-06 12:17 ` Richard Zidlicky
2004-04-06 13:28 ` Brad Campbell
2004-04-06 20:23 ` Filip Navara
2004-04-07 4:34 ` Brad Campbell
2004-04-07 7:59 ` Filip Navara
2004-04-07 8:24 ` Brad Campbell
2004-04-07 8:47 ` Grzegorz Kulewski
2004-04-07 17:50 ` Richard Zidlicky
2004-04-07 9:40 ` Filip Navara
2004-04-06 14:00 ` Jamie Burns
2004-04-06 19:00 ` Fabrice Bellard
2004-04-05 9:38 ` Jean-Michel POURE
2004-04-05 10:23 ` John R. Hogerhuis
-- strict thread matches above, loose matches on Subject: below --
2004-04-05 15:19 Mike Nordell
2004-04-05 20:40 ` Filip Navara
2004-04-05 21:05 ` John R. Hogerhuis
2004-04-05 21:15 ` Filip Navara
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=200404051130.04164.Rudi@LYRIKpage.de \
--to=rudi@lyrikpage.de \
--cc=jhoger@pobox.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).