From: "K. Richard Pixley" <rich.pixley@palmsource.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] config file support
Date: Mon, 23 Oct 2006 10:50:05 -0700 [thread overview]
Message-ID: <453D00CD.6010307@palmsource.com> (raw)
In-Reply-To: <200610221751.50317.rob@landley.net>
[-- Attachment #1: Type: text/plain, Size: 801 bytes --]
Rob Landley wrote:
> On Wednesday 18 October 2006 2:42 pm, Chuck Brazie wrote:
>
>> Is there any work going on now to add config file support?
>>
>> Chuck Brazie
>> brazie@us.ibm.com
>>
> As a random end-user, I really like being able to run qemu without a config
> file, configuring it entirely on the command line. I'd be highly
> disappointed if qemu turned into another Wine.
Except that I never do. Instead, I write a trivial shell script since I
can never remember the command line options, much less type them in
consistently.
What's the difference between a shell script to cover qemu and a
#!/bin/qemu config file? Seems to me they both address roughly the same
issues with roughly the same considerations. Am I missing any
significant functionality differences?
--rich
[-- Attachment #2: Type: text/html, Size: 1294 bytes --]
next prev parent reply other threads:[~2006-10-23 17:50 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-18 18:42 [Qemu-devel] config file support Chuck Brazie
2006-10-18 19:51 ` [Qemu-devel] " Anthony Liguori
2006-10-19 18:03 ` Fabrice Bellard
2006-10-22 21:51 ` [Qemu-devel] " Rob Landley
2006-10-23 10:58 ` Christian MICHON
2006-10-23 11:48 ` Jan Marten Simons
2006-10-23 12:24 ` Paul Brook
2006-10-23 17:50 ` K. Richard Pixley [this message]
2006-10-23 20:39 ` Rob Landley
2006-10-23 20:58 ` Paul Brook
2006-10-23 21:01 ` K. Richard Pixley
2006-10-23 21:17 ` M. Warner Losh
2006-10-23 20:42 ` André Braga
-- strict thread matches above, loose matches on Subject: below --
2006-10-20 17:55 [Qemu-devel] Config " Chuck Brazie
2006-10-21 0:12 ` Johannes Schindelin
2006-10-21 10:00 ` Ricardo Almeida
2006-10-21 11:40 ` Stefan Weil
2006-10-22 9:51 ` Johannes Schindelin
2006-10-22 17:01 ` Flavio Visentin
2006-10-22 17:19 ` Martin Guy
2006-10-22 18:27 ` Paul Brook
2006-10-23 20:01 ` Rob Landley
2006-10-23 20:29 ` Paul Brook
2006-10-23 22:22 ` Rob Landley
2006-10-23 23:33 ` Paul Brook
2006-10-24 9:04 ` Rob Landley
2006-10-24 10:47 ` Flavio Visentin
2006-10-24 12:05 ` Christian MICHON
2006-10-24 16:46 ` Blue Swirl
2006-10-24 20:38 ` Christian MICHON
2006-10-24 23:32 ` Rob Landley
2006-10-25 8:20 ` Johannes Schindelin
2006-10-24 0:11 ` andrzej zaborowski
2006-10-24 0:34 ` Paul Brook
2006-10-24 0:12 ` Re[2]: " Paul Sokolovsky
2006-10-24 0:36 ` Paul Brook
2006-10-24 1:38 ` Re[2]: " Paul Sokolovsky
2006-10-24 2:31 ` Paul Brook
2006-10-24 8:37 ` Christian MICHON
2006-10-24 23:28 ` Rob Landley
2006-10-25 0:18 ` Re[2]: " Paul Sokolovsky
2006-10-25 15:01 ` Paul Brook
2006-10-26 14:31 ` Rob Landley
2006-10-27 19:33 ` Re[2]: " Paul Sokolovsky
2006-10-28 0:08 ` Paul Brook
2006-10-24 23:28 ` Rob Landley
2006-10-21 18:00 ` David Baird
2006-10-23 18:25 [Qemu-devel] config " Ben Taylor
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=453D00CD.6010307@palmsource.com \
--to=rich.pixley@palmsource.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.