Gilad Ben-Yossef wrote:
Omer Zak wrote:
Another solution is to use VMware. It has checkpoint feature, which allows you to save the state of your virtual machine (including the states of any files on virtual disks) at a certain time; and then revert to the checkpoint at a future time.
Well, while this does sound like an overkill to me, if you go this path you might want to consider qemu, which also has "snapshot" and "copy on right" disks mode and is free as opposed to the proprotiery VMware (it also supports more platforms).
I routinely use it in a virtual machine used for cross-compiling software. This way I can be sure that I get a pristine virtual machine for the next time I build software.
hm... what an interesting concept. Isn't it be easier to maintain the state of the files by building all the cross-compiled enviornment to sit in some specified place /opt/toolchain/ and simply tarball it for next time or event create a whole chroot jail rather then mainting the state of the OS + proccessor + disks?
What if the toolchain is itself multi-platform - some of the tools run under Linux, and other tools - under MS-Windows.
It is trivial to clean up (and ensure that it is clean) the Linux part of the build, but the MS-Windows part is a different (and sadder) story altogether.
--- Omer
My own blog is at http://www.livejournal.com/users/tddpirate/
My opinions, as expressed in this E-mail message, are mine alone. They do not represent the official policy of any organization with which I may be affiliated in any way. WARNING TO SPAMMERS: at http://www.zak.co.il/spamwarning.html
================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
