Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!apple!radius!lemke From: lemke@radius.com (Steve Lemke) Newsgroups: comp.sys.mac.hardware Subject: Re: System 7.0 and RAM Message-ID: <1441@radius.com> Date: 26 Apr 91 01:09:51 GMT References: <1991Apr25.190940.15729@cbnewsk.att.com> <1991Apr25.212632.22379@neon.Stanford.EDU> Distribution: usa Lines: 18 philip@pescadero.stanford.edu (Philip Machanick) writes: >There are other reasons to keep the whole of VM on disk. If you get a total ^^^^^^^^^^^^^^^^^^ >system crash, it's nice to be able to see a reasonably recent snapshot ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >of system state. ^^^^^^^^^^^^^^^^ This is a nice idea, and would be even nicer if there were some utility that could crawl through the VM file and actually tell you something about what happened. As it is now, I would imagine when you reboot you'll lose all that useful information, and even if you boot from another disk, there really aren't any tools for dissecting the remains of your preserved VM file. -- ----- Steve Lemke, KC6QDT - Software Engineering, Radius Inc., San Jose ----- ----- Reply to: lemke@radius.com -- U.C. Santa Barbara ECE Class of '89 ----- ----- "I'm not a UNIX wizard, but I play the Postmaster at radius.com." -----