On Tuesday, 02/05/2008 at 11:52 EST, David Boyes <[EMAIL PROTECTED]> wrote: > Specious argument: pages are in shared core at any time as well, but > that's a different argument. AFAIK, CP paging decisions are not directly > accessible inside a guest in any programmatic form (other than > generating bad behavior to get yourself paged out, which is > counterproductive if you're trying to intercept things), whereas spool > access is fairly easy.
Now you've confused me. Access to your own spool files is easy. Access to spool files belonging to others is not. Nor is it possible to access another virtual machine's memory without its cooperation. In fact, data is more secure in memory than it is on disk since, once on disk, anyone with a connection to the disk can see it without restriction. I contest your statement that "spool access is fairly easy". Not by an unprivileged user, it isn't. Alan Altmark z/VM Development IBM Endicott ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
