From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JOkkS-0003Q8-2k for qemu-devel@nongnu.org; Mon, 11 Feb 2008 21:19:52 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JOkkP-0003Pw-N6 for qemu-devel@nongnu.org; Mon, 11 Feb 2008 21:19:50 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JOkkP-0003Pt-Hn for qemu-devel@nongnu.org; Mon, 11 Feb 2008 21:19:49 -0500 Received: from ug-out-1314.google.com ([66.249.92.170]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JOkkP-0000qv-Bf for qemu-devel@nongnu.org; Mon, 11 Feb 2008 21:19:49 -0500 Received: by ug-out-1314.google.com with SMTP id m2so402437uge.4 for ; Mon, 11 Feb 2008 18:19:47 -0800 (PST) Message-ID: Date: Tue, 12 Feb 2008 03:19:47 +0100 From: "andrzej zaborowski" Subject: Re: [Qemu-devel] [PATCH] Allow default network type to be determined from an environmental variable In-Reply-To: <200802111817.31058.rob@landley.net> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <478A80B8.7070708@us.ibm.com> <200801192110.11295.paul@codesourcery.com> <200802111817.31058.rob@landley.net> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: Anthony Liguori , Paul Brook On 12/02/2008, Rob Landley wrote: > On Saturday 19 January 2008 15:10:09 Paul Brook wrote: > > It's also extremely hard to determine what environment a user is running. > > Type "set" with no arguments. (I admit bash 3.x throws insane amounts of crap > into this by default, but any program that's exposed to the FSF for an > extended period of time bloats beyond recognition.) I think Paul Brook was concerned about a situation where a user reports a problem saying X 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 :) I personally can accept not knowing what environment the user is running though. You'll never be able to reproduce 100% of user-reported bugs (and usually you won't even try), and any new way of configuring qemu that you introduce (say, config files) will have the same problem. -- Please do not print this email unless absolutely necessary. Spread environmental awareness.