From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Gc3wG-0005AB-JH for qemu-devel@nongnu.org; Mon, 23 Oct 2006 13:50:16 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Gc3wF-00059j-Ou for qemu-devel@nongnu.org; Mon, 23 Oct 2006 13:50:16 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Gc3wF-00059b-J4 for qemu-devel@nongnu.org; Mon, 23 Oct 2006 13:50:15 -0400 Received: from [12.7.175.14] (helo=mx2.palmsource.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1Gc3wF-0000zv-HD for qemu-devel@nongnu.org; Mon, 23 Oct 2006 13:50:15 -0400 Message-ID: <453D00CD.6010307@palmsource.com> Date: Mon, 23 Oct 2006 10:50:05 -0700 From: "K. Richard Pixley" MIME-Version: 1.0 Subject: Re: [Qemu-devel] config file support References: <200610221751.50317.rob@landley.net> In-Reply-To: <200610221751.50317.rob@landley.net> Content-Type: multipart/alternative; boundary="------------080507040805050604090304" 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 This is a multi-part message in MIME format. --------------080507040805050604090304 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Rob Landley wrote: > On Wednesday 18 October 2006 2:42 pm, Chuck Brazie wrote: > >> Is there any work going on now to add config file support? >> >> Chuck Brazie >> brazie@us.ibm.com >> > As a random end-user, I really like being able to run qemu without a config > file, configuring it entirely on the command line. I'd be highly > disappointed if qemu turned into another Wine. Except that I never do. Instead, I write a trivial shell script since I can never remember the command line options, much less type them in consistently. What's the difference between a shell script to cover qemu and a #!/bin/qemu config file? Seems to me they both address roughly the same issues with roughly the same considerations. Am I missing any significant functionality differences? --rich --------------080507040805050604090304 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Rob Landley wrote: 
On Wednesday 18 October 2006 2:42 pm, Chuck Brazie wrote:
  
Is there any work going on now to add config file support?

Chuck Brazie 
brazie@us.ibm.com
    
As a random end-user, I really like being able to run qemu without a config 
file, configuring it entirely on the command line.  I'd be highly 
disappointed if qemu turned into another Wine.
Except that I never do.  Instead, I write a trivial shell script since I can never remember the command line options, much less type them in consistently.

What's the difference between a shell script to cover qemu and a #!/bin/qemu config file?  Seems to me they both address roughly the same issues with roughly the same considerations.  Am I missing any significant functionality differences?

--rich
--------------080507040805050604090304--