From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33)
	id 1C2b96-00039m-G5
	for qemu-devel@nongnu.org; Wed, 01 Sep 2004 15:51:52 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33)
	id 1C2b94-00039a-Uo
	for qemu-devel@nongnu.org; Wed, 01 Sep 2004 15:51:52 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.33) id 1C2b94-00039X-Qx
	for qemu-devel@nongnu.org; Wed, 01 Sep 2004 15:51:50 -0400
Received: from [204.183.119.5] (helo=web.dslmyway.com)
	by monty-python.gnu.org with esmtp (Exim 4.34) id 1C2b3f-0003gW-Tf
	for qemu-devel@nongnu.org; Wed, 01 Sep 2004 15:46:16 -0400
Received: from fred.soliddesign.net (fred.soliddesign.net [10.2.3.220])
	by dash.soliddesign.net (Postfix) with ESMTP id 3D19B5751D
	for <qemu-devel@nongnu.org>; Wed,  1 Sep 2004 14:46:09 -0500 (EST)
Subject: Re: [Qemu-devel] Qemu development schedule?
From: Joe Batt <Joe@soliddesign.net>
In-Reply-To: <A2872254-FC4C-11D8-8B6F-000A95D874F4@mac.com>
References: <000501c48eda$a026ab40$20649c3f@computername>
	<1093903154.26682.44.camel@aragorn>
	<002001c48ee5$456d6a30$20389c3f@computername>
	<Pine.LNX.4.58.0408311335470.23761@wgmdd8.biozentrum.uni-wuerzburg.de>
	<000601c48f73$752b00a0$03389c3f@computername>
	<1093969628.2835.98.camel@fred.soliddesign.net>
	<005301c48f82$067c5af0$82389c3f@computername>
	<A2872254-FC4C-11D8-8B6F-000A95D874F4@mac.com>
MIME-Version: 1.0
Content-Type: text/plain
Message-Id: <1094067968.6164.11.camel@fred.soliddesign.net>
Date: Wed, 01 Sep 2004 14:46:08 -0500
Content-Transfer-Encoding: 7bit
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org

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