qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Ricardo Almeida" <ric.almeida@gmail.com>
To: "Daniel P. Berrange" <berrange@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] make /usr/bin/qemu the native arch
Date: Sun, 8 Jul 2007 18:04:51 +0100	[thread overview]
Message-ID: <8a6cde920707081004j42b61cf5sc887b0c6ef636991@mail.gmail.com> (raw)
In-Reply-To: <20070708163550.GA11527@redhat.com>

On 7/8/07, Daniel P. Berrange <berrange@redhat.com> wrote:
> On Sun, Jul 08, 2007 at 02:21:02PM +0200, Robert Millan wrote:
> > Shouldn't /usr/bin/qemu be an alias for qemu-system-$(ARCH), where $(ARCH) is
> > the native architecture?  Defaulting to i386 doesn't make much sense nowadays,
> > specially since x86_64 is gradually obsoleting it.
>
> Management tools for QEMU will have come to rely on existing semantics of
> /usr/bin/qemu being i386.

Why?! If they rely on 386 I think they should directly use
qemu-system-i386... If they manage in an architecture independent way
then use the qemu link...

> Changing this for merely cosmetic reasons would

Not cosmetic, logic...

> cause significant technical complications because tools would then have to
> try and detect whether /usr/bin/qemu were native or i386.

See my previous why?! ;)

> Thus I see no
> real functional/technical benefit to changing it, and plenty of downside.

If it's more logic, you have a functional benefit. And for the
downside, I don't see them except for non-logic assumptions ;)

Regards,
Ricardo Almeida

  reply	other threads:[~2007-07-08 17:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-08 12:21 [Qemu-devel] [PATCH] make /usr/bin/qemu the native arch Robert Millan
2007-07-08 16:35 ` Daniel P. Berrange
2007-07-08 17:04   ` Ricardo Almeida [this message]
2007-07-08 20:16     ` Daniel P. Berrange
2007-07-11 18:54       ` andrzej zaborowski
  -- strict thread matches above, loose matches on Subject: below --
2007-08-01 19:53 Robert Millan

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=8a6cde920707081004j42b61cf5sc887b0c6ef636991@mail.gmail.com \
    --to=ric.almeida@gmail.com \
    --cc=berrange@redhat.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).