From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thiemo Seufer Subject: Re: [kvm-devel] Re: Storing command line options in images Date: Mon, 13 Aug 2007 20:39:27 +0100 Message-ID: <20070813193927.GA21215@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> Reply-To: qemu-devel@nongnu.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: kvm-devel@lists.sourceforge.net, qemu-devel@nongnu.org To: Jorge =?iso-8859-1?Q?Luc=E1ngeli?= Obes Return-path: Content-Disposition: inline In-Reply-To: <59abf66e0708101841i76e26a35vcbc8df14b21f1ac0@mail.gmail.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org List-Id: kvm.vger.kernel.org Jorge Luc=E1ngeli Obes wrote: [snip] > When I read Avi's TODO, I basically thought about getting rid of the > long command lines I had to store in scripts. I wanted to write that > command line once, and then forgetting about it, until I needed to > change it. 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 where qemu.cfg is a file which contains the command line arguments. (This is also low-maintenance, as it allows to re-use the existing parser. No need for duplicated logic.) > 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. > All that said, I rethought Anthony's idea of storing plain text in the > image and with proper tools, it can work out. Requiring "proper tools" doesn't leave much of a point for plain text. Thiemo From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IKgDZ-000729-D2 for qemu-devel@nongnu.org; Mon, 13 Aug 2007 16:08:49 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IKgDX-0006yz-NA for qemu-devel@nongnu.org; Mon, 13 Aug 2007 16:08:48 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IKgDX-0006yh-IT for qemu-devel@nongnu.org; Mon, 13 Aug 2007 16:08:47 -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 1IKgDX-00017B-5I for qemu-devel@nongnu.org; Mon, 13 Aug 2007 16:08:47 -0400 Date: Mon, 13 Aug 2007 20:39:27 +0100 From: Thiemo Seufer Subject: Re: [kvm-devel] [Qemu-devel] Re: Storing command line options in images Message-ID: <20070813193927.GA21215@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> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: <59abf66e0708101841i76e26a35vcbc8df14b21f1ac0@mail.gmail.com> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jorge =?iso-8859-1?Q?Luc=E1ngeli?= Obes Cc: kvm-devel@lists.sourceforge.net, qemu-devel@nongnu.org Jorge Luc=E1ngeli Obes wrote: [snip] > When I read Avi's TODO, I basically thought about getting rid of the > long command lines I had to store in scripts. I wanted to write that > command line once, and then forgetting about it, until I needed to > change it. 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 where qemu.cfg is a file which contains the command line arguments. (This is also low-maintenance, as it allows to re-use the existing parser. No need for duplicated logic.) > 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. > All that said, I rethought Anthony's idea of storing plain text in the > image and with proper tools, it can work out. Requiring "proper tools" doesn't leave much of a point for plain text. Thiemo