[comp.sys.xerox] Noticing files using LYRIC on the Hard Disk

tim@kansas-state.CSNET (Tim Hines) (12/18/87)

Noticing files in Lyric:

   I installed a fresh Lyric SYSOUT and created a backup on another volume.
   I then copied several files, e.g. font files, to the hard disk and
   saved my SYSOUT.

   A problem seems to exist if something happens to your original SYSOUT,
   i.e. when it cannot be booted. The same problem exists when using
   (VMEM.PURE.STATE T).

   -------
       Scenario:
             SYSOUT 1                   SYSOUT 2
                copied font files           copied font files only
                created lisp files
                ...
   -------

   If SYSOUT 1 can no longer be used and SYSOUT 2 is booted your files
   that have been created in SYSOUT 1 will not be noticed in SYSOUT 2
   using either FILEBROWSER.

   The same problem exists when you set VMEM.PURE.STATE to T and then
   RE-BOOT after doing a (LOGOUT T). Any files that you had copied to
   to the hard disk prior to doing a (LOGOUT T) will not be found when
   you re-boot.

   This problem does not exist in KOTO, so why is it a problem in LYRIC
   and is there a way to fix this problem?

   I need a way to fix this problem since we usually run with the state
   of (VMEM.PURE.STATE T).
   We would appreciate any comments or answers to the problem stated above.
   Thank you for any responses.

   Tim
   Kansas State University

dering.pasa@XEROX.COM (12/19/87)

Tim,

It sounds as if you have not put a directory on your Lispfiles volume.  In the
case where no directory is defined, Lisp emulates the rigid disk with a core
device called {PSEUDO-DSK}.   Since the core device is contained in virtual
memory, it lasts only as long as you keep your virtual memory image. (When you
have VMEM.PURE.STATE turned on you do not save your virtual memory over logout,
so any files copied to DSK will disappear.)

Create the directory with (CREATEDSKDIRECTORY volumename).   You can check for a
directory with (LISPDIRECTORYP volumename.)  See the "File System" section of
the appropriate Users Guide for more details.

Judy Dering

gandalf@russell.STANFORD.EDU (Juergen Wagner) (12/19/87)

I had this behaviour when I used {PseudoDSK} instead of the {DSK}<lispfiles>
volume. Be sure you write on a partition different from the one you're keeping
your working sysout in. The fact that this behaviour occurs especially in
connection with the VM.PURE.STATE switch set makes me believe that your 
problem is of that kind. If not, please ignore my message.

-- 
Juergen Wagner,			        gandalf@Russell.Stanford.edu
Center for the Study of Language and Information (CSLI), Stanford CA