From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Dvu9U-0007uD-5A for qemu-devel@nongnu.org; Fri, 22 Jul 2005 05:49:08 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Dvu9Q-0007sl-Q9 for qemu-devel@nongnu.org; Fri, 22 Jul 2005 05:49:05 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Dvu9Q-0007ro-KZ for qemu-devel@nongnu.org; Fri, 22 Jul 2005 05:49:04 -0400 Received: from [195.129.94.252] (helo=srv94-252.ip-tech.ch) by monty-python.gnu.org with esmtp (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA:24) (Exim 4.34) id 1DvuCh-00045V-L3 for qemu-devel@nongnu.org; Fri, 22 Jul 2005 05:52:28 -0400 Message-ID: <42E0BF78.40005@kberg.ch> Date: Fri, 22 Jul 2005 11:42:16 +0200 From: Mike Kronenberg MIME-Version: 1.0 Subject: Re: [Qemu-devel] news on the OS X cocoa port References: <42DF6E93.3010705@kberg.ch> <41e41e7a0507210312259ae3d5@mail.gmail.com> <42DF9604.2090503@kberg.ch> <31C44163-0A44-491F-90CD-70D35E19EA10@cordney.com> <20050721151959.GA4011@jbrown.mylinuxbox.org> <42E0A578.70305@kberg.ch> In-Reply-To: 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: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org [snip] >> Right now I'm using .plist(property lists), which is very common in >> OS X, because you can read them back directly in to an Array or a >> Dictionaty. It's a standardized XML File. >> I'm a big fan of XML, but I'm also very much Intrested in having a >> compatible package over all platforms. >> I see advantage in XML, because it's a lot more flexible and accurat >> in storing your Data - well it was defined exactly for that pourpose :) > > > Fully agree. > >> >> My packages look like this: >> ~/Documents/QEMU/Freedos.qemu/configuration.plist >> ~/Documents/QEMU/Freedos.qemu/hda.img >> ~/Documents/QEMU/Freedos.qemu/saved.vm >> ~/Documents/QEMU/Freedos.qemu/thumbnail.png >> or: >> ~/Documents/QEMU/ReactOS 15412.qemu/configuration.plist >> ~/Documents/QEMU/ReactOS 15412.qemu/hda.img >> ~/Documents/QEMU/ReactOS 15412.qemu/saved.vm >> ~/Documents/QEMU/ReactOS 15412.qemu/thumbnail.png > > > What about .qvm instead of .qemu ? Ok for me. >> >> They can nicely be ziped. >> >> A sample configuration .plist: >> >> > "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> >> >> >> -boot >> 1 >> -cdrom >> >> -fda >> >> -hda >> /Users/mike/Documents/qemu/images/2gb_win2k.img >> -m >> 128 >> cpu >> 0 >> custom >> >> name >> win2ksp4 >> status >> shutdown >> >> > > > I assume cpu is the system the image is designed for, f.e. > x86? What about some additional keys like author, date of creation, > email if someone f.e. downloaded the image from the web and has > problems getting it to run?! This is right from Q, so its no real proposal, just to show the advantages of xml. cpu stands for the guest PC architekture. I would propose 4 dicts in a containing dict: - Description (PC Name, Platform) - Arguments (with the real qemu arguments) - Author (FreeOSZoo go go go!) - Temp (to store temporary "nice to have" hints for a specific port) > Hey, FreeOSZoo'ers, what do you think would be also nice to save in > the xml regarding distribution on your platform? > According to your site: > > ToDO List: > [...] > > 1. Create a FreeOSZoo hotdelivery XML format, gathering all > information needed to download and install FreeOSZoo images. We > hope that the FreeOSZoo hotdelivery XML format will allow the > next generation of QEMU GUIs to connect to a distribution site > and download the needed files automatically. We plan the XML > file to deliver the following information: > * Available mirrors for download > * Bittorent trackers > * Host operating systems requirements > * Guest operating systems requirements > * List of free software bundled > * Upgrading facilities over the Internet > * Targeted audience (home use, ...) > * Links to a gallery of screenshots > * Links to tutorials and help systems > * Links to live video presentations > [snip] Mike