From: Stefan Weil <weil@mail.berlios.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC][PATCH] Rename qemu into qemu-system-i386 and install a compat symlink
Date: Sun, 19 Apr 2009 13:22:39 +0200 [thread overview]
Message-ID: <49EB097F.6050100@mail.berlios.de> (raw)
In-Reply-To: <49EA030A.8090104@codemonkey.ws>
Anthony Liguori schrieb:
> Aurelien Jarno wrote:
>> For historical reasons, qemu system on i386 is called qemu instead of
>> qemu-system-i386. This seems to confuse users.
>>
>> This patch installs it as qemu-system-i386, and create a compatibility
>> symlink qemu -> qemu-system-i386 as some tools may call it that way.
>> We can change or remove this symlink after a few releases when all the
>> tools have migrated to this new name.
>>
>
> I agree.
>
> Regards,
>
> Anthony Liguori
>
I agree partially.
For the current situation, qemu-system-i386 is reasonable,
and a symbolic link to qemu for non-Windows platforms is
a good solution.
For the (maybe far) future, I'd prefer to have a qemu executable
which is either a frontend to the different user and system
emulation executables or which replaces all these executables.
This new qemu could auto-detect the target architecture
from -M (cpu parameter) or from ELF file argument.
It could also auto-detect user or system mode.
Calling the correct backend qemu-xxx is then straight forward.
And finally, keeping qemu (with enhanced functionality)
would also allow to keep the existing documentation unchanged:
qemu-doc.texi has lots of references to qemu!
Regards,
Stefan Weil
next prev parent reply other threads:[~2009-04-19 11:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-18 16:01 [Qemu-devel] [RFC][PATCH] Rename qemu into qemu-system-i386 and install a compat symlink Aurelien Jarno
2009-04-18 16:42 ` Anthony Liguori
2009-04-19 11:22 ` Stefan Weil [this message]
2009-04-19 11:32 ` andrzej zaborowski
2009-04-18 17:22 ` Andreas Färber
2009-04-18 17:45 ` Aurelien Jarno
2009-04-18 18:21 ` Stefan Weil
2009-04-18 21:12 ` Aurelien Jarno
2009-04-18 22:11 ` Anthony Liguori
2009-04-18 23:43 ` Re : " Sylvain Petreolle
2009-04-19 2:50 ` Jamie Lokier
2009-04-18 18:34 ` Blue Swirl
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=49EB097F.6050100@mail.berlios.de \
--to=weil@mail.berlios.de \
--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).