On Mon, 8 Jan 2001, Benjamin Scott <[EMAIL PROTECTED]> wrote:
...
> > I have the older vmware 1.x, but it appears in the 2.x there seemes to
> > be a feature where you can store a VM in a "suspended" state (like a
> > laptop's suspend to disk). If that works as I hope, that would save
> > the boot up time of 'doze. Have you ever used this?
>
> I've used it. It takes a long time to suspend to
> disk, likely as much time as a slim Windows config would take to boot.
> Resumes are reasonably quick. YMMV.
The advantage for the "sandbox thingie" is that you do this long
suspend time to disk files _once_ to freeze the sandbox state and then,
if I've understood you correctly, that info is supplied to vmware as
startup data.
Glad to hear the resume is reasonably quick. Of course the vmware
process has to malloc(3) 20-30 MB of RAM for the VM, but if the whole
restore is not more than twice that time, that's pretty good. Perhaps
less time than a StarOffice "boot" :-)
I don't quite know how to get the "untrusted" .EXE data into the
virtual disk safely in the suspended state, but perhaps something could
be cooked up.
> It works as well as Windows normally works during
> suspend/resume, which is to say, not very.
That's too bad. Maybe with a simple enough state (minimal HD, no apps
running etc) for the sandbox initial state it would be a bit more
reliable.
Best,
Karl
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
