qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Christian MICHON" <christian.michon@gmail.com>
To: qemu-devel@nongnu.org
Cc: kvm-devel@lists.sourceforge.net,
	"Laurent Vivier" <Laurent.Vivier@bull.net>,
	"Jorge Lucángeli Obes" <t4m5yn@gmail.com>
Subject: Re: [kvm-devel] [Qemu-devel] Re: Storing command line options in images
Date: Tue, 14 Aug 2007 22:46:22 +0200	[thread overview]
Message-ID: <46d6db660708141346j65718d7ere38473e5c6a3f377@mail.gmail.com> (raw)
In-Reply-To: <20070814200757.GA7685@networkno.de>

yet colinux >= 0.7.1 is using I believe a similar approach for passing its
parameters...

quoting the readme: "colinux-daemon @example.conf"

and this is what I use on a daily basis to compile detaolb on colinux
(which I test later using qemu).

On 8/14/07, Thiemo Seufer <ths@networkno.de> wrote:
> Jorge Lucángeli 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
>
>
>


-- 
Christian
--
http://detaolb.sourceforge.net/, a linux distribution for Qemu

  reply	other threads:[~2007-08-14 20:46 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 [this message]
2007-08-13 19:39             ` Thiemo Seufer
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=46d6db660708141346j65718d7ere38473e5c6a3f377@mail.gmail.com \
    --to=christian.michon@gmail.com \
    --cc=Laurent.Vivier@bull.net \
    --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).