Museum

Home

Lab Overview

Retrotechnology Articles

Online Manuals

⇒ lsd(1M) — DG/UX 4.31

Media Vault

Software Library

Restoration Projects

Artifacts Sought

Related Articles

crash(1M)



     lsd(1M)                    DG/UX 4.31                     lsd(1M)



     NAME
          lsd - load a system dump from tape

     SYNOPSIS
          lsd [ -s ] [ -d dir_name ] input_dev

          dir_name  The directory into which the dump files will be
                    loaded; default = the current directory.
          input_dev The pathname of a no-rewind tape device that will
                    be used to load the dump.

     DESCRIPTION
          Lsd loads the contents of a system dump tape set that was
          produced after a kernel panic or hang.  Multi-tape sets are
          supported; lsd prompts for the next tape when it needs to
          change volumes.

          A dump tape set normally has two tape files:  the memory
          image and a cpio archive.  If the memory image is too large
          for a single tape, it will be broken up into separate tape
          files across as many tapes as are necessary to store it.

          Options are:

          -s   Specify that the cpio archive is not present on the
               tape or should be skipped.

          -d   Load the dump files into the specified directory.  If
               dir_name does not exist, lsd creates it.

     EXAMPLE
          lsd /dev/rmt/0n

     SEE ALSO
          crash(1M) and Installing and Managing the DG/UX System.

     DIAGNOSTICS
          Error diagnostics are routed to standard error; other
          diagnostics are routed to standard output.  All are self-
          explanatory.

     NOTE
          The memory image (ordinarily named mainmemory) consists of
          the contents of the system's physical memory at the time of
          the panic or hang.  The cpio archive consists of files that
          were appended to the final dump tape after the system dump
          concluded.  Usually, the archive contains the system's
          kernel image (ordinarily named dgux) and any test programs
          or files relevant to the system panic or hang.  If both the
          memory image and the kernel image are available, the
          crash(1M) command can be used for post-mortem debugging of
          the system.



     Licensed material--property of copyright holder(s)         Page 1



Typewritten Software • bear@typewritten.org • Edmonds, WA 98026