<div class="gmail_quote">On Thu, Mar 12, 2009 at 4:12 PM, Dave Bauer <span dir="ltr"><<a href="mailto:dave.bauer@gmail.com">dave.bauer@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="gmail_quote"><div class="im"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="gmail_quote"><div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
But really, all we need to be doing is producing .vmdk files (virtual<br>
disk images) for our SoaS snapshots. These files can be loaded in any<br>
of VMware, VirtualBox and Parallels, and can be used with QEMU after a<br>
command line conversion step.<br>
</blockquote></div><div>
</div></div></blockquote></div></div></blockquote></div><br>In any case, even if it was this easy (other seem to report otherwise), it's more steps than an educator should have to perform. The idea is that we can provide them with prepackaged, no extra-fluff-needed executables, *as well* as in raw image formats. <br>
<br>Moreover, VMDK files are (IIRC) hard to generate programmatically, whereas COW/QEMU images can be generated easilly as part of a build script.<br>-- <br>Luke Faraone<br><a href="http://luke.faraone.cc">http://luke.faraone.cc</a><br>