BOOT(8S) — UNIX Programmer’s Manual
NAME
boot − run a standalone program or bring up DYNIX
SYNOPSIS
From the powerup monitor:
on SCED-based systems:
∗ b [ flag ] [ program [ arg ] ... ]
on SSM-based systems:
---> bh [ ’[flag]program [ arg ] ...’ ]
DESCRIPTION
boot brings up the DYNIX operating system, or loads other standalone programs into memory.
flag is the value of the configuration flag. Standalone programs (including boot and the DYNIX kernel) interpret various bits of the configuration flag. On SCED systems, if flag is not specified, a default value is taken from the most recent wf powerup monitor command. On SSM systems, if flag is not specified as part of the bootstring it defaults to zero. On SSM systems, there must not be any space characters between flag and program. Additionally the single quotes are required only if the optional arg field is provided.
If the lowest bit of the configuration flag is one (that is, if the configuration flag is odd), boot will ask for the name of the program to be loaded into memory. Otherwise, the name is taken from the command line, or (if not present) the value specified the last time the bootstring was set from the powerup monitor. For SCED systems, the command for setting the bootstring is wn0=bootstring and for SSM systems, the command is bh os=’bootstring’.
The name of the program is given in standalone file notation. Standalone file notation is represented as:
dv(un,su) file
where dv is the name of the device driver, un and su are the unit and subunit parameters (interpreted by the device driver), and file is the name of the file to be run. Supported device drivers for SCED systems are sd, ts, xt and zd. Supported device drivers for SSM systems are wd and tm. In general, for disk drivers, un selects among the various drives, su selects a particular disk partition, and file is a DYNIX file name relative to the top level directory of the DYNIX file system located in the selected partition. For tape drivers, un selects among the various drives, su selects a particular file on the tape (bounded by EOF tape marks), and file is unused.
boot loads the program into memory, displays the allocation of text, data, and bss (uninitialized data), and then begins execution of the program. When the program exits, the powerup monitor resumes.
Arguments for the program may follow the program name, as long as they are separated from the program name by at least one space. boot makes the entire (uninterpreted) command line available to the invoked program. The invoked program must then parse the command line to determine the arguments.
SEE ALSO
DYNIX System Administration Guide, DYNIX Diagnostics User’s Guide
DYNIX