A/UX® System Administrator's Reference Sections 1M, 7, and 8

launch(8) launch(8)
NAME
launch - launch an NUX kernel from the NUX Startup
environment
SYNOPSIS
launch [-a] [-d] [-f] [-m] [-r] [-v] [-s] [pathname]
launch [-n] [-d] [-f] [-m] [-r] [-v] [-s] [pathname]
DESCRIPTION
1
launch loads an NUX kernel into memory and transfers control
to the kernel. launch can only be run from the NUX Startup
application shell (see StartupShell(8)). As launch
transfers control to the kernel, it passes a SCSI ID, a logical unit
number, and slice zero as parameters. The kernel uses these
parameters to locate the root file system (ROOTDEV).
When no pathname is specified, launch uses the filename on the
first line of the ASCII file / next unix. The specified kernel
(from the command line or from / next unix) is then checked
for an autoconfiguration match.
autoconfig{lM) is run when a software module is present in
the kernel, but the required hardware is missing. (Note that
autoconfig will NOT be run when hardware is present and the
software is missing.)
If autoconfig needs to be run, then the kernel newunix is
launched instead and a flag is set indicating that autoconfig is
needed.
The format of pathname can vary. If you wish to include a device
specification the format is:
(device-spec) path
device-spec is described in detail in StartupShell(8). It consists
of three comma-separated numbers enclosed in parentheses.
The first number is the SCSI ID for a disk, the second is the logical
unit (usually zero), and the final number is a slice number. To
illustrate, the following command line launches the sunix kernel
located within the file system in slice 2 of the disk that is assigned
SCSI ID 1:
launch (1,O,2)/src/sys/psu/sunix
In this example, the kernel would use slice 0 of the disk with SCSI
ID 1 as the location for the root partition. So even though the kernel
is loaded from a file system in slice 2, the root file system is
February, 1990
RevisionC