From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1Eu208-00089Q-RY
	for qemu-devel@nongnu.org; Wed, 04 Jan 2006 01:20:00 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1Eu206-00087a-Jv
	for qemu-devel@nongnu.org; Wed, 04 Jan 2006 01:20:00 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Eu206-00087S-Ho
	for qemu-devel@nongnu.org; Wed, 04 Jan 2006 01:19:58 -0500
Received: from [194.126.101.98] (helo=HOT-Bounce1.hot.ee)
	by monty-python.gnu.org with esmtp (Exim 4.34) id 1Eu21S-0003RT-74
	for qemu-devel@nongnu.org; Wed, 04 Jan 2006 01:21:22 -0500
Received: from mail.neti.ee (Relay8 [192.168.1.27])
	by HOT-Bounce1.hot.ee (Postfix) with ESMTP id BFBBA19199F
	for <qemu-devel@nongnu.org>; Wed,  4 Jan 2006 07:51:10 +0200 (EET)
Message-ID: <43BB6224.9020507@vision.ee>
Date: Wed, 04 Jan 2006 07:50:28 +0200
From: martin <martin@vision.ee>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] qemu and configuration file?
References: <200512312120.43014.bepi@adria.it>
	<200601032249.41640.bepi@adria.it>
In-Reply-To: <200601032249.41640.bepi@adria.it>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
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

  If we'd go for a config file at all with such a complicated structure, i see no reasons why to 
choose anything else than xml for it. We have tons of xml libs that can be used for gui's (think 
perl, tk, python etc...). Certainly better every dude writing it's own XuPeRpArSeR that will be 
broken and compatible after a major change in qemu ...
  Another choice would be the pure rc (just 'item = value' lines) without any supersmart blocks.

xml style or rc style, please no hack in betweeen :)

martin


Giuseppe Della Bianca wrote:
> Hi.
> 
> My idea is this:  
> - qemu start 
> - set up of the hardcode parameters 
> - reading of the configuration file and set up of the parameters 
> - set up of the parameters of command line 
> 
> Example of configuration file:
> [general]
>   ....
>   [vlan0]
>     ip= x.y.x.w
>     mac= l:m:n:o
>     ....
>   [/vlan0]
> [/general]
> 
> [suse.img]
>   ....
>   [vlan3]
>     mac= h:j:k:l
>     ....
>   [/vlan3]
> [/suse.img]
> 
> [win.img]
>   ....
>   [vlan2]
>     mac= z:x:c:v
>     ....
>   [/vlan2]
> [/win.img]
> 
> Result: 
> - full compatibility with every version of qemu 
> - more flexibility 
> - possibility to set up the hardcode parameters 
> - possibility of parameters personalized for every image 
> 
> One similar thing, with smaller flexibility, is possible 
>  without modify qemu and using one series of bash script.
> 
> Comments are welcomes (at least one "it does not interest to us"). 
> 
> Regards.
> 	Gdb 
> 
> 
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel