From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IL308-0002jr-BC for qemu-devel@nongnu.org; Tue, 14 Aug 2007 16:28:28 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IL306-0002jF-Iy for qemu-devel@nongnu.org; Tue, 14 Aug 2007 16:28:27 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IL306-0002jC-Eh for qemu-devel@nongnu.org; Tue, 14 Aug 2007 16:28:26 -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 1IL306-0001li-43 for qemu-devel@nongnu.org; Tue, 14 Aug 2007 16:28:26 -0400 Date: Tue, 14 Aug 2007 21:07:57 +0100 From: Thiemo Seufer Subject: Re: [kvm-devel] [Qemu-devel] Re: Storing command line options in images Message-ID: <20070814200757.GA7685@networkno.de> References: <46BC9CDB.3080900@qumranet.com> <46BCB1DA.6060102@codemonkey.ws> <46BCBF73.5060406@qumranet.com> <46BCC666.6050406@codemonkey.ws> <59abf66e0708101841i76e26a35vcbc8df14b21f1ac0@mail.gmail.com> <46C01C8D.3060304@qumranet.com> <46C02216.2030503@bull.net> <46C1BCAC.9030203@bull.net> <59abf66e0708141202t4eaf009cs4596cc76a164e3de@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: <59abf66e0708141202t4eaf009cs4596cc76a164e3de@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, Laurent Vivier , qemu-devel@nongnu.org Jorge Luc=E1ngeli Obes wrote: [snip] > Quoting Thiemo, this '@' thing was "a feature which is now implemented > in the GNU toolchain". That's why I tried it. Now I would like to know > what he did to get it working. It would certainly be an useful > feature, even if it does not exactly suit our purposes. Apparently I managed to create some misunderstanding. :-) The @file feature was implemented in/for the _tools_ of the GNU toolchain. It is not meant to become a general feature of all linux userland applications. Thiemo