From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IKjWb-0003j1-Ph for qemu-devel@nongnu.org; Mon, 13 Aug 2007 19:40:41 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IKjWa-0003iA-3r for qemu-devel@nongnu.org; Mon, 13 Aug 2007 19:40:41 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IKjWZ-0003i3-RI for qemu-devel@nongnu.org; Mon, 13 Aug 2007 19:40:39 -0400 Received: from phoenix.bawue.net ([193.7.176.60] helo=mail.bawue.net) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1IKjWZ-00034o-9l for qemu-devel@nongnu.org; Mon, 13 Aug 2007 19:40:39 -0400 Date: Tue, 14 Aug 2007 00:31:13 +0100 From: Thiemo Seufer Subject: Re: [kvm-devel] [Qemu-devel] Re: Storing command line options in images Message-ID: <20070813233112.GC21215@networkno.de> References: <59abf66e0708092155t2e3cd5o32f23c018bed65af@mail.gmail.com> <46BC8C18.6020108@codemonkey.ws> <46BC9CDB.3080900@qumranet.com> <46BCB1DA.6060102@codemonkey.ws> <46BCBF73.5060406@qumranet.com> <46BCC666.6050406@codemonkey.ws> <59abf66e0708101841i76e26a35vcbc8df14b21f1ac0@mail.gmail.com> <20070813193927.GA21215@networkno.de> <0CDF49F7-76CD-45C6-97A6-FA7B6893FD60@ecs.soton.ac.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0CDF49F7-76CD-45C6-97A6-FA7B6893FD60@ecs.soton.ac.uk> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Philip Boulain Cc: qemu-devel@nongnu.org Philip Boulain wrote: > On 13 Aug 2007, at 20:39, Thiemo Seufer wrote: >> Instead of inventing great and wonderfully complicated schemes, the >> most sensible way I can think of is to recycle a feature which is now >> implemented in the GNU toolchain, and apparently stems from Windows: >> qemu @qemu.cfg > > I'm not familiar with that. Is it just GNU bash shorthand for qemu `cat > qemu.cfg` ? I don't think it has anything to do with bash. Apparently Windows(NT) cmd.exe introduced this as a way to avoid unwieldy command lines. Cygwin (or MingGW?) added the same to their tools in order to avoid command line length problems. Not so long ago it was implemented for gcc and binutils, both as a way to pass overlong argument lists and to allow for easier scripting. >>> I wanted an image to be self-contained as much as possible. >>> That's what I set to achieve. >> Which tends to collect all the complexity in a single piece. >> That seems to be the common problem of the option discussed here. > > As far as I can tell, this is desirable for easy distribution of images to > other machines; this is pretty much my only objection to the 'directory' > idea, which is otherwise a nice, clean solution. (If not, I can't really > see what's wrong with a one-liner sh script alongside the image, which is > basically what has been reinvented.) It would be a sh script plus a cmd script plus whatever OS X may need some day, all of them copying the same option line. @file would avoid that (and allow generic wrapper scripts). Thiemo