From: Thiemo Seufer <ths@networkno.de>
To: "Jorge Lucángeli Obes" <t4m5yn@gmail.com>
Cc: kvm-devel@lists.sourceforge.net, qemu-devel@nongnu.org
Subject: Re: [kvm-devel] [Qemu-devel] Re: Storing command line options in images
Date: Mon, 13 Aug 2007 20:39:27 +0100 [thread overview]
Message-ID: <20070813193927.GA21215@networkno.de> (raw)
In-Reply-To: <59abf66e0708101841i76e26a35vcbc8df14b21f1ac0@mail.gmail.com>
Jorge Lucángeli 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
next prev parent reply other threads:[~2007-08-13 20:08 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-10 4:55 [Qemu-devel] Storing command line options in images Jorge Lucángeli Obes
2007-08-10 16:02 ` [Qemu-devel] Re: [kvm-devel] " Anthony Liguori
2007-08-10 17:14 ` Avi Kivity
2007-08-10 18:43 ` [kvm-devel] [Qemu-devel] " Anthony Liguori
2007-08-10 19:41 ` Avi Kivity
2007-08-10 20:11 ` Anthony Liguori
2007-08-11 1:41 ` Jorge Lucángeli Obes
2007-08-13 8:55 ` Avi Kivity
2007-08-13 9:19 ` Laurent Vivier
2007-08-13 9:27 ` Christian MICHON
2007-08-14 14:18 ` Markus Hitter
2007-08-14 14:31 ` Laurent Vivier
2007-08-14 19:02 ` Jorge Lucángeli Obes
2007-08-14 20:07 ` Thiemo Seufer
2007-08-14 20:46 ` Christian MICHON
2007-08-13 19:39 ` Thiemo Seufer [this message]
2007-08-13 20:26 ` Christian MICHON
2007-08-13 22:21 ` Philip Boulain
2007-08-13 22:27 ` [Qemu-devel] Re: [kvm-devel] " Jernej Simončič
2007-08-13 23:31 ` [kvm-devel] [Qemu-devel] " Thiemo Seufer
2007-08-14 14:26 ` Philip Boulain
2007-08-14 3:17 ` Anthony Liguori
2007-08-14 4:39 ` Jorge Lucángeli Obes
2007-08-14 7:44 ` Kevin Wolf
2007-08-14 7:46 ` Laurent Vivier
2007-08-15 21:26 ` Segher Boessenkool
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=20070813193927.GA21215@networkno.de \
--to=ths@networkno.de \
--cc=kvm-devel@lists.sourceforge.net \
--cc=qemu-devel@nongnu.org \
--cc=t4m5yn@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).