HP-UX Reference (11i v1 05/09) - 1M System Administration Commands A-M (vol 3)
h
hpux(1M) hpux(1M)
manager lan manages remote boot through the HP28652A NIO based LAN interface (formerly
lan1).
Remote boot is currently supported on this card only and not on any CIO-based LAN card. The manager
tape manages tape drives via SCSI (formerly tape2
).
The hardware path in a devicefile specification is a string of numbers, each suffixed by slash, (
/), followed
by a string of numbers separated by dots (
.), each number identifying a hardware component notated
sequentially from the bus address to the device address. A hardware component suffixed by a slash indi-
cates a bus converter and may not be necessary on your machine. For example, in w
/x.y.zwis the
address of the bus converter, x is the address of the MID-BUS module, y is the CIO slot number, and z is
the HP 27111 bus address.
The minor number, n,inadevicefile specification controls driver-dependent functionality. (See the manual,
Configuring HP-UX for Peripherals, for minor-number bit assignments of specific drivers).
File names are standard HP-UX path names. No preceding slash (
/) is necessary and specifying one will
not cause problems.
Defaults
Default values chosen by
hpux to complete a command are obtained through a sequence of steps. First,
any components of the command specified explicitly are used. If the command is not complete,
hpux
attempts to construct defaults from information maintained by pdc (see pdc(1M)). If sufficient information
to complete the command is unavailable, the autoexecute file is searched. If the search fails, any
remaining unresolved components of the command are satisfied by hard-coded defaults.
There is no hard-coded default choice for a manager; if none can be chosen, hpux reports an error.
When the hardware path to the boot device is not specified,
hpux defaults to information maintained by
pdc. The hardware path element has no hard-coded default.
If the minor number element is not supplied, hpux takes its default from the autoexecute file. Failing
that, the hard-coded default of 0 is used.
For the
boot command, a devicefile specification without a file name indicates that the boot device does
not contain an HP-UX file system. hpux interprets this as a NULL (instead of missing) file name and does
not search for a default. If the entire devicefile specification is missing,
hpux searches for a default; either
the
autoexecute file contents or the hard-coded default is chosen.
There are two possible hard-coded default devicefile specifications. One hard-coded default devicefile
specification is
/vmunix. The other hard-coded default devicefile specification is
/stand/vmunix.
If you have a LVM system where the boot volume and the root volume are on different logical volumes, the
kernel would be
/vmunix. This is because the boot volume will be mounted under /stand when the sys-
tem is up.
For all other configurations, the kernel would be /stand/vmunix
.
The search order for the hard-coded defaults is
/stand/vmunix
and then /vmunix.
boot Operation
The boot operation loads an object file from an HP-UX file system or raw device as specified by the
optional devicefile. It then transfers control to the loaded image.
Any missing components in a specified devicefile are supplied with a default. For example, a devicefile of
vmunix.new would actually yield:
disc(8.0.0;0)vmunix.new
and a devicefile of (8/0/19/0.14.0)/stand/vmunix
, for booting from the disk at Ultra Wide SCSI
address 14, would yield
disc(8/0/19/0.14.0;0)/stand/vmunix
Regardless of how incomplete the specified devicefile may be, boot announces the complete devicefile
specification used to find the object file. Along with this information, boot gives the sizes of the TEXT,
DATA, and BSS, segments and the entry offset of the loaded image, before transferring control to it.
Section 1M−−322 Hewlett-Packard Company − 2 − HP-UX 11i Version 1: September 2005