From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Gc6Zs-0001Fd-Fb for qemu-devel@nongnu.org; Mon, 23 Oct 2006 16:39:20 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Gc6Zr-0001EY-Su for qemu-devel@nongnu.org; Mon, 23 Oct 2006 16:39:19 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Gc6Zr-0001EH-F5 for qemu-devel@nongnu.org; Mon, 23 Oct 2006 16:39:19 -0400 Received: from [71.162.243.5] (helo=grelber.thyrsus.com) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1Gc6Zr-0002FY-FR for qemu-devel@nongnu.org; Mon, 23 Oct 2006 16:39:19 -0400 From: Rob Landley Subject: Re: [Qemu-devel] config file support Date: Mon, 23 Oct 2006 16:39:00 -0400 References: <200610221751.50317.rob@landley.net> <453D00CD.6010307@palmsource.com> In-Reply-To: <453D00CD.6010307@palmsource.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200610231639.00717.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 On Monday 23 October 2006 1:50 pm, K. Richard Pixley wrote: > 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? The shell script works now, and you're proposing breaking it? > Seems to me they both address roughly the same > issues with roughly the same considerations. Using a *.PIF file is the Windows way. Using the command line is Linux. > Am I missing any significant functionality differences? So you'd have no trouble configuring kde's file type associations to open arbitrary "*.img" files with qemu when you click on them if you couldn't do this entirely from the command line? > --rich Rob -- "Perfection is reached, not when there is no longer anything to add, but when there is no longer anything to take away." - Antoine de Saint-Exupery