From: assemblywizard@gmail.com   
      
   There is always screen memory, I can't even imagine a paranoid sys admin   
   who would have an argument against you having access on your own   
   screen--can't remember 'em all--but on the DEC VAX way back when, you   
   could always gain access through ncurses...   
      
   ... now, if you wanted access to someone's else's terminal screen   
   memory--that might be a problem...    
      
   Warmest regards,   
   John   
      
   "Jim Leonard"  wrote in message   
   news:1117766030.467142.82430@g44g2000cwa.googlegroups.com...   
   > John Smith wrote:   
   >> Oh I have, if you can prove you need the privilege, the sys admin   
   >> will   
   >> give it to you--if not, they are watching you--time to line up a   
   >> better   
   >> job...   
   >   
   > Heh... I *am* a sysadmin (seriously, it's my day job).  No need to   
   > wear   
   > a tinfoil hat... we sysadmins don't "watch" people unless they give us   
   > a reason to.  Like John Cusack's character in Gross Pointe Blank:  "If   
   > I show up at your door, chances are you did something to bring me   
   > there."  :-)   
   >   
   > My original point, of course, was that you can't use screen memory for   
   > array storage if your screen memory isn't directly accessable.  In   
   > general, it's best to avoid clever tricks unless your solution needs   
   > to   
   > be highly specialized in some particular way.  (Or unless it's   
   > completely for fun, like 128-byte competitions.)   
   >   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)