From: Joe Batt <Joe@soliddesign.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Qemu development schedule?
Date: Wed, 01 Sep 2004 14:46:08 -0500 [thread overview]
Message-ID: <1094067968.6164.11.camel@fred.soliddesign.net> (raw)
In-Reply-To: <A2872254-FC4C-11D8-8B6F-000A95D874F4@mac.com>
On Wed, 2004-09-01 at 14:25, Kai Cherry wrote:
> On Aug 31, 2004, at 1:42 PM, Jeebs wrote:
> ...
> That would be a start. I suggested something even more simple just
> minutes ago: a config file :)
> Most simple UI in the world, but very, very helpful.
>
> qemu -c <somefilefullofoptions>
>
> Would that be helpful? (It would be commented nice for ya, as well.)
And every computer I've ever used already has a method to do that. In
DOS I used batch files, VMS command files, Unix shell scripts, windows
shortcuts.
What is the difference between creating a configuration file that has
qemu options or making a shortcut with qemu options? Either way you
have a file with expressions that have to be looked up in a manual.
I prefer the short cut method, to eliminate a file. With a
configuration file, I have to have qemu.exe, qemu.conf, and the qemu
shortcut to click on. Since I have to have the shortcut anyway, why
have the configuration file? Adding layers does not make it easier.
It could even be self describing... 'qemu --help'. For even more
information, you could 'man qemu'!
Now, if someone were to write a qemu configuration wizard that for some
on foreseen reason can't modify the shortcut, then I'm on board.
Joe
next prev parent reply other threads:[~2004-09-01 19:51 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-30 21:44 [Qemu-devel] Qemu development schedule? Jeebs
2004-08-30 21:59 ` John R. Hogerhuis
2004-08-30 22:51 ` Jeebs
2004-08-31 11:59 ` Johannes Schindelin
2004-08-31 15:58 ` Jeebs
2004-08-31 16:27 ` Joe Batt
2004-08-31 17:42 ` Jeebs
2004-09-01 19:25 ` Kai Cherry
2004-09-01 19:33 ` andrej
2004-09-01 19:46 ` Joe Batt [this message]
2004-09-01 20:34 ` Mike Tremoulet
2004-09-01 20:46 ` Kai Cherry
2004-09-01 20:35 ` Kai Cherry
2004-09-02 20:46 ` Jim C. Brown
2004-09-03 7:52 ` [Qemu-devel] Filegetopt (Was: Qemu development schedule?) Renzo Davoli
2004-08-31 16:32 ` [Qemu-devel] Qemu development schedule? Johannes Schindelin
2004-08-31 17:40 ` Jeebs
2004-09-01 15:43 ` Lionel Ulmer
2004-09-01 17:03 ` John R. Hogerhuis
2004-09-01 19:07 ` Kai Cherry
2004-09-02 10:20 ` Info
2004-08-31 17:42 ` John R. Hogerhuis
2004-08-31 19:07 ` andrej
2004-08-31 19:44 ` Kai Cherry
2004-08-30 22:07 ` Hetz Ben Hamo
2004-08-30 22:59 ` Jeebs
2004-08-30 23:34 ` John R. Hogerhuis
2004-08-31 9:21 ` Kai Cherry
2004-08-31 10:15 ` Patrick Mauritz
2004-08-31 10:23 ` Kai Cherry
2004-08-31 17:23 ` Gianni Tedesco
2004-08-31 19:08 ` Kai Cherry
2004-09-01 20:53 ` Magnus Damm
2004-08-31 20:27 ` Fabrice Bellard
2004-08-31 21:50 ` René Korthaus
2004-09-01 22:04 ` Jim C. Brown
2004-08-31 22:02 ` Patrick Mauritz
2004-09-01 21:58 ` Jim C. Brown
2004-09-02 7:26 ` Lionel Ulmer
2004-09-02 20:56 ` Jim C. Brown
2004-09-02 23:28 ` Lionel Ulmer
2004-09-03 0:07 ` Jim C. Brown
2004-09-03 8:32 ` Fabrice Bellard
2004-09-03 7:29 ` Adrian Smarzewski
2004-09-03 8:28 ` Fabrice Bellard
2004-09-02 23:53 ` Daniel Serpell
2004-09-03 0:13 ` Jim C. Brown
2004-09-03 1:35 ` John R. Hogerhuis
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=1094067968.6164.11.camel@fred.soliddesign.net \
--to=joe@soliddesign.net \
--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.