[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [kvm-devel] [Qemu-devel] Re: Storing command line options in images

From: Philip Boulain
Subject: Re: [kvm-devel] [Qemu-devel] Re: Storing command line options in images
Date: Tue, 14 Aug 2007 15:26:55 +0100

On 14 Aug 2007, at 00:31, Thiemo Seufer wrote:
Philip Boulain wrote:
On 13 Aug 2007, at 20:39, Thiemo Seufer wrote:
...implemented in the GNU toolchain, and apparently stems from Windows:
  qemu @qemu.cfg
I'm not familiar with that. Is it just GNU bash shorthand for qemu `cat
qemu.cfg`  ?

I don't think it has anything to do with bash.

Apparently Windows(NT) cmd.exe introduced this as a way to avoid unwieldy command lines. Cygwin (or MingGW?) added the same to their tools in order to avoid command line length problems. Not so long ago it was implemented
for gcc and binutils...

Ugh. This is in-application magic that does a pre-parsing step on argv []? I'm suddenly being flooded with horrible memories of how Win-DOS requires each individual application to implement its own wildcards in arguments, and how these implementations were inevitably inconsistent in ways that stabbed you in the face.

Maybe QEMU /should/ have a "...and read this file as arguments..." argument, but this really doesn't seem a good way to do it. "-c qemu.cfg" is a lot less ambiguous, as you don't have to worry about whether an '@' in an argument is an include command, or a literal, e.g. part of a filename (it could be either, and escaping it at the shell level won't help).


reply via email to

[Prev in Thread] Current Thread [Next in Thread]