From: Segher Boessenkool <segher-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
To: Laurent Vivier <Laurent.Vivier-6ktuUTfB/bM@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
Thiemo Seufer <ths-eH4hzgmiRX8dwXzzRB9H2Q@public.gmane.org>,
qemu-devel-qX2TKyscuCcdnm+yROfE0A@public.gmane.org
Subject: Re: [Qemu-devel] Re: Storing command line options in images
Date: Wed, 15 Aug 2007 23:26:47 +0200 [thread overview]
Message-ID: <1dbd1c6c19219b2e9c037189a19f1fbd@kernel.crashing.org> (raw)
In-Reply-To: <46C15DCE.1000205-6ktuUTfB/bM@public.gmane.org>
>>> 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
>
> IMHO, it should be implemented at the shell level, not qemu level,
> like "*" is.
The shell _does_ implement it: qemu `cat qemu.cfg` :-)
If you want "@" anyway, you can pick up the code from libiberty
(or just build with libiberty).
Segher
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
prev parent reply other threads:[~2007-08-15 21:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-10 4:55 Storing command line options in images Jorge Lucángeli Obes
[not found] ` <59abf66e0708092155t2e3cd5o32f23c018bed65af-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-08-10 16:02 ` Anthony Liguori
[not found] ` <46BC8C18.6020108-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2007-08-10 17:14 ` [Qemu-devel] " Avi Kivity
[not found] ` <46BC9CDB.3080900-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-08-10 18:43 ` Anthony Liguori
[not found] ` <46BCB1DA.6060102-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2007-08-10 19:41 ` Avi Kivity
[not found] ` <46BCBF73.5060406-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-08-10 20:11 ` Anthony Liguori
[not found] ` <46BCC666.6050406-rdkfGonbjUSkNkDKm+mE6A@public.gmane.org>
2007-08-11 1:41 ` Jorge Lucángeli Obes
[not found] ` <59abf66e0708101841i76e26a35vcbc8df14b21f1ac0-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-08-13 8:55 ` Avi Kivity
[not found] ` <46C01C8D.3060304-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-08-13 9:19 ` Laurent Vivier
2007-08-13 9:27 ` [kvm-devel] " Christian MICHON
2007-08-14 14:18 ` Markus Hitter
[not found] ` <F213D784-7927-4233-BD3E-57A808D31FE7-5aU9hSJ5JWgb1SvskN2V4Q@public.gmane.org>
2007-08-14 14:31 ` [Qemu-devel] " Laurent Vivier
[not found] ` <46C1BCAC.9030203-6ktuUTfB/bM@public.gmane.org>
2007-08-14 19:02 ` Jorge Lucángeli Obes
[not found] ` <59abf66e0708141202t4eaf009cs4596cc76a164e3de-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-08-14 20:07 ` Thiemo Seufer
[not found] ` <20070814200757.GA7685-eH4hzgmiRX8dwXzzRB9H2Q@public.gmane.org>
2007-08-14 20:46 ` Christian MICHON
2007-08-13 19:39 ` [kvm-devel] " Thiemo Seufer
[not found] ` <20070813193927.GA21215-eH4hzgmiRX8dwXzzRB9H2Q@public.gmane.org>
2007-08-13 20:26 ` [Qemu-devel] " Christian MICHON
2007-08-14 3:17 ` Anthony Liguori
2007-08-14 4:39 ` Jorge Lucángeli Obes
2007-08-14 7:46 ` [kvm-devel] " Laurent Vivier
[not found] ` <46C15DCE.1000205-6ktuUTfB/bM@public.gmane.org>
2007-08-15 21:26 ` Segher Boessenkool [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1dbd1c6c19219b2e9c037189a19f1fbd@kernel.crashing.org \
--to=segher-xvmvhmargas8u2djnn8i7kb+6bgklq7r@public.gmane.org \
--cc=Laurent.Vivier-6ktuUTfB/bM@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=qemu-devel-qX2TKyscuCcdnm+yROfE0A@public.gmane.org \
--cc=ths-eH4hzgmiRX8dwXzzRB9H2Q@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox