From: Paul Brook <paul@codesourcery.com>
To: andrzej zaborowski <balrogg@gmail.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Allow default network type to be determined from an environmental variable
Date: Tue, 12 Feb 2008 02:46:37 +0000 [thread overview]
Message-ID: <200802120246.37899.paul@codesourcery.com> (raw)
In-Reply-To: <fb249edb0802111819k1985d8a2ua35a897c5ffec7ae@mail.gmail.com>
> I think Paul Brook was concerned about a situation where a user
> reports a problem saying FOO is not working when running "qemu -hda ..."
> and suddenly the number of things that may have triggered the bug has
> grown by the size of the environment. Even if you manage to tell the
> user to pastebin the environment, it may have changed by then. I'm
> pretty sure Paul knows how to list the env variables :)
Indeed. I see many, many users complain that qemu dies because of SDL errors.
Almost without fail this is because they're running qemu in a different
environment (e.g. under su as root), so are using an environment that can't
connect to their X server.
Running "set | grep QEMU" is fine, except that it has to be done in the same
environment as qemu runs in. You'd be surprised how many users are incapable
of doing what seems to be a straightforward task.
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.
Paul
next prev parent reply other threads:[~2008-02-12 2:46 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 [this message]
2008-02-12 3:47 ` Anthony Liguori
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=200802120246.37899.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=aliguori@us.ibm.com \
--cc=balrogg@gmail.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).