Of course a VM currently is easier to manage but a decent sandbox system should be an option where you don't need to have a full blown "Guest OS" running - specifically if you just want to test out some applications. Plenty of uses for a sandbox which don't necessarily need a full blown VM for testing. What abut also testing different software versions and comparing -real pain to re-install each time. IMO a Sandbox should definitely have the option of persistence - at start up the sandbox application should be able to load an old one or a brand new one with a user prompt at start up. I don't think that's entirely true - for example what about software that requires a reboot after install or testing configuration changes which may also require a re-boot -or even basic testing applications which use different sets of data. Why do you want to do this? What are you trying to accomplish? If you can answer those questions, the community may have some useful suggestions for you. But then, you'd lose what had changed in the surrounding OS and filesystem around the sandbox. That said, I suppose you could take an image backup with the Sandbox active and then restore that backup to get the sandbox back. The whole purpose of a sandbox is not to persist data.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |