From: Philip Boulain <prb@ecs.soton.ac.uk>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [kvm-devel] [PATCH][RFC] Allowing QEMU to directly execute a directory (and storing command line options in it)
Date: Mon, 03 Sep 2007 12:10:20 +0100 [thread overview]
Message-ID: <1188817820.15382.9.camel@panther> (raw)
In-Reply-To: <CC77BFD7-A721-4E5A-8A7F-4F73AD92FDB6@df.lth.se>
On Mon, 2007-09-03 at 12:01 +0200, Christian Brunschen wrote:
> On 3 Sep 2007, at 11:19, Philip Boulain wrote:
> > What's the difference between having to hack about a plain-text,
> > few-lines configuration file, and a plain-text, few-lines shell
> > script?
> The same shells are not (at least by default) available on all
> platforms.
You only need sh, because all you're doing is an exec, which covers all
POSIX platforms. For Windows, use a shortcut.
> Basically, requiring a shell script means that you have to meta-
> program around qemu itself, whereas a configuration file means you're
> writing something within the context of qemu (and thus don't have to
> venture outside qemu's domain).
Given that the goal is "simple", I'd consider this a plus. 95% of
UNIX-like systems is glue.[1]
> 2) if 'foo' is a directory:
> verify that 'foo' is in fact a vm bundle directory...
If this is going to move from frontends to QEMU itself, given that the Q
devs have already created a QEMU VM bundle format, it makes sense to use
theirs. It's a sensible format, consistent at least with OS X bundle
conventions. (Not sure about GNUStep bundles, but given that their both
NeXT offspring, I doubt there's much difference.)
> Saying that 'Q already handles this' means that any other program
> that wants to offer a similar ease-of-use would have to be able to
> read and interpret Q's configuration file format.
I don't see a problem with this.
> If instead there is
> a wrapper-neutral format, then each wrapper can use that.
This is what Q bundles should be absorbed as. For "simple", there are
shell scripts. For "complete", there are bundles, and Q's format is a
good one to absorb as "the QEMU bundle format". I don't see the point in
a config format which adds nothing but complexity over a shell script.
LionsPhil
1. This figure drawn from entirely unauthoritative sources. ;)
next prev parent reply other threads:[~2007-09-03 11:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-31 18:19 [Qemu-devel] [PATCH][RFC] Allowing QEMU to directly execute a directory (and storing command line options in it) Jorge Lucángeli Obes
2007-08-31 18:54 ` [Qemu-devel] Re: [kvm-devel] " Anthony Liguori
2007-08-31 19:05 ` Jorge Lucángeli Obes
2007-08-31 19:13 ` Anthony Liguori
2007-09-01 11:02 ` Markus Hitter
2007-09-01 14:26 ` Luke -Jr
2007-09-01 14:49 ` Andreas Färber
2007-09-01 14:39 ` Andreas Färber
2007-09-01 18:45 ` Jorge Lucángeli Obes
2007-09-01 19:52 ` Andreas Färber
2007-09-01 20:26 ` Jorge Lucángeli Obes
2007-09-03 9:19 ` Philip Boulain
2007-09-03 10:01 ` Christian Brunschen
2007-09-03 11:10 ` Philip Boulain [this message]
2007-09-03 11:40 ` Andreas Färber
2007-09-03 13:54 ` Andreas Färber
2007-09-03 14:54 ` Luke -Jr
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=1188817820.15382.9.camel@panther \
--to=prb@ecs.soton.ac.uk \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).