Lisa Denia wrote: > yes, sure. But I don't really want to switch everytime I want to create > a new .vmdk file. > Is there a reason why that feature is only supported in the proprietary > version?
Of course there is. Was a decision made when that feature was implemented. Note that the VMDK disk image format code (part of OSE) supports this already, just that OSE contains no way of reaching that code. There are lots of changes to the general (virtual) disk image infrastructure in the pipeline, so this might be reconsidered in that context. Also if someone would want to contribute a patch it'll be hard to integrate probably, as the code is in the middle of a huge reorganization. Is there a particular reason why you absolutely need to use VirtualBox OSE? The PUEL license conditions are pretty liberal, just read them. We tried to make them as non-lawyer understandable as possible. -- Dr. Klaus Espenlaub innotek GmbH, http://www.innotek.de _______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
