qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Allow default network type to be determined from an environmental variable
Date: Mon, 11 Feb 2008 21:47:40 -0600	[thread overview]
Message-ID: <47B116DC.8080507@us.ibm.com> (raw)
In-Reply-To: <200802120246.37899.paul@codesourcery.com>

Paul Brook wrote:
> This is similar to why I dislike qemu automagically guessing settings. If you 
> force everything to be explicitly specified (or use fixed defaults) then 
> there's no margin for error. If behaviour depends on external factors then 
> you can guarantee the person stuck between you (the "expert") and the 
> misbehaving application will have no clue how to determine or control those 
> external factors.
>   

Come on, if the concern is being able to determine the users 
environment, there are very well understood ways to handle this.  Just 
have QEMU log all of the configuration parameters to some log file upon 
startup like so many other applications do.

If people don't like using environmental variables, I can accept that.  
Let's not pretend though that the reason is that we're protecting the 
end users :-)

Regards,

Anthony Liguori

> Paul
>   

  reply	other threads:[~2008-02-12  3:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-13 21:20 [Qemu-devel] [PATCH] Allow default network type to be determined from an environmental variable Anthony Liguori
2008-01-19 21:10 ` Paul Brook
2008-01-19 22:40   ` Anthony Liguori
2008-01-19 22:47   ` M. Warner Losh
2008-02-12  0:17   ` Rob Landley
2008-02-12  1:42     ` Paul Brook
2008-02-12  2:19     ` andrzej zaborowski
2008-02-12  2:46       ` Paul Brook
2008-02-12  3:47         ` Anthony Liguori [this message]
2008-02-12 12:27           ` Paul Brook

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=47B116DC.8080507@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=paul@codesourcery.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).