systemtape(1M)                 DG/UX 5.4R3.00                 systemtape(1M)


NAME
       systemtape - build a bootable DG/UX system tape

SYNOPSIS
       systemtape [ -q ] [ -x ] [ -f tapedevice ] [ -r rootfilesystem ] [
       -u usrfilesystem ] [ -s standdirectory ] [ -n packageshortname ]

DESCRIPTION
       Starting in DG/UX (Trademark) 5.4R3.00 the systemtape command builds
       a bootable DG/UX(Tm system tape using the values of rootfilesystem
       and usrfilesystem.  You must be superuser in order to use this
       command.  This command copies all locally mounted files and
       directories in the rootfilesystem and the usrfilesystem to the
       tapedevice in a format that can be loaded in standalone mode.  A
       systemtape is useful for restoring the root and/or usr filesystems.
       This command also creates a /usr/release filelist file and a
       /usr/options . name file.  Systemtapes made on DG/UX 5.4R3.00 and
       later systems should not be loaded onto systems running a pre DG/UX
       5.4R3.00 revision.

       Options are:

       -v     This option will enable verbose mode. Verbose mode is
              interactive and asks for confirmation that a tape is in the
              tapedevice.  The default mode is the verbose mode.

       -q     This option turns off the (default) verbose mode.

       -b bootfile
              This option specifies the bootfile image that is written to
              the systemtape.  The default is "/usr/stand/boot.aviion".

       -f tapedevice
              This option indicates which tape device to use during this
              process.  The specification is an absolute path. Do not
              specify a no-rewind device.  The default value is
              "/dev/rmt/0".

       -n packageshortname
              This option indicates what to name the package on the tape.
              The default is "dgux". Packages with the name "dgux" can only
              be loaded in standalone mode. In general, the files in root
              associated with the DG/UX Operating System should only be
              loaded in standalone mode.  Loading a systemtape of the root
              and/or usr filesystem in standamong mode is likely to fail.

       -r rootfilesystem
              This option specifies the root file system to be written to
              tape.  The specification is an absolute path. The default is
              "/".

       -s standfile
              This option specifies the standalone image file to be that is
              written to the systemtape.  The specification is an absolute



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

systemtape(1M)                 DG/UX 5.4R3.00                 systemtape(1M)


              path. The default is "/usr/stand/sysadm".

       -u usrfilesystem
              This option specifies the /usr file system to be written to
              tape.  The specification is an absolute path. The default is
              "/usr".

DIAGNOSTICS
       systemtape exits with a value of 0 if the system tape is successfully
       created.  If the command is unable to access the tape device or read
       the requested files, the exit value is 1.

SEE ALSO
       sysadm(1M), and admpackage(1M).

NOTES
       This command must be run by the superuser.  In addition, the
       designated rootfilesystem and usrfilesystem must be readable by
       the superuser.

       Pre DG/UX 5.4R3.00 systems should not load a systemtape made with a
       DG/UX 5.4R3.00 (or later) systemtape command. The 5.4R3.00 standalone
       utility that is written to tape and is used to load the systemtape
       expects the system to be using virtual disks. Pre 5.4R3.00 systems
       make use of logical disks.  In addition, pre 5.4R3.00 systems will
       not recognize the [*nosrv*] format and will fail doing the load
       operation if the root filesystem is not at least three times the size
       of the root filesystem contents on tape.

       Before invoking systemtape, you must ensure that the correct file
       systems are mounted.

       Files that are owned by users and groups not found in the local
       passwd(4) and group(4) databases will cause a warning message to be
       generated when the tape is unloaded.

       systemtape creates tapes in the DG/UX [*nosrv*] format rather that
       the standard DG/UX [*] format. This means that files in the root
       filesystem on a systemtape are not copied into the OS client
       /srv/release areas when the tape is loaded onto a system.  This
       eliminates the need for a large amount of free space in the root
       filesystem in order to load a systemtape.

       The revision string in the tape table of contents reflects the date
       and time the systemtape was written. The format of the revision
       string is yymmdd.HHMM. The admpackage -olist command can be used to
       display the tape table of contents.

       When a systemtape is loaded the contents of the tape are simply
       overloaded onto whatever currently resides in the root and usr
       filesystems.  Files on the system which are not on the systemtape
       will persist after a systemtape load.





Licensed material--property of copyright holder(s)                         2