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
_______________________________________________
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
