HPUXBOOT(1M) — Series 800 Only

NAME

hpux − HP-UX bootstrap and installation utility

SYNOPSIS

hpux [−a devicefile]... [−fnumber] [−istring] [−o] [−r]
[boot] [devicefile]
hpux install
hpux ls [devicefile]
hpux −v
hpux copy devicefile devicefile

DESCRIPTION

Hpux is the HP−UX specific initial system loader (isl(1M)) utility for bootstrap and first−time installation. It supports three operations: boot, install, and ls. The last operation listed, copy, is obsolete and may not work on your system. The boot operation loads an object file from an HP−UX file system or raw device and transfers control to the loaded image. The install operation is used during first time installation. It attempts to execute an install image from a properly formatted installation device. The ls operation lists the contents of HP−UX directories in a format similar to ls(1). The copy operation copies data between HP−UX files and/or raw devices. This operation is not recommended since it may damage your file systems.

The command sequences for all operations are presented under SYNOPSIS above. They may be either entered interactively to isl or present in an isl autoexecute file. The first sequence performs the boot operation. The second performs the install operation. The third performs the ls operation. The fourth returns the release and version numbers of hpux. The last performs the copy operation.

NUMBERS

Hpux accepts numbers (i.e. numeric constants) in many of its options. Numbers follow the C language notation for decimal, octal, and hexadecimal constants. A leading 0 (zero) implies octal and a leading 0x or 0X implies hexadecimal. For example, 037, 0x1F, 0X1f, and 31 all represent the same number, decimal 31.

DEVICEFILES

Hpux boot, ls, and copy operations accept devicefile specifications, which have the following format:

manager(w/x.y.z;n,s)filename

They are called devicefiles because they are composed of a device name part and a file name part. In the device part, manager(w/x.y.z;n,s), manager is the name of an HP 9000 Series 800 I/O System manager (i.e. device driver), for example disc0. W/x.y.z is the physical hardware path to the device, identifying bus converters, slot numbers, and hardware addresses. (Bus converter specifications are necessary only for models with bus converters such as the Model 850. hpux only allows one level of bus converters). N is the minor number which controls manager dependent functionality. S is the file skip count. For tape1 devices, this parameter describes how many files must be skipped (from the beginning of the tape) before the desired file can be accessed. It has a default value of 0, and is completely ignored for other devices. The file name part, filename, is a standard HP−UX path name. In a devicefile specification, the only required component is the hardware path. All other components are optional. Some hpux operations have defaults for particular components. A devicefile specification containing a device part only specifies a raw device. A devicefile specification containing a file name implies that the associated device part names a device containing an HP−UX file system. The named file resides in that file system. For example, a typical boot devicefile specification is disc0(2/4.0.0;0)hp−ux.

Managers

Currently, hpux supports the disc0, disc2, disc1, lan1, and tape1 managers. Disc0 manages all CS−80 discs connected via HP−IB, including cartridge tape devices, and disc2 manages all CS−80 discs connected via the HP 27111. Disc1 manages all CS−80 discs connected via NIO HP−IB, including cartridge tape devices. Lan1 manages remote boot through the HP28652A NIO based lan card. Remote boot is currently supported on this card only and not on any CIO based lan card. Tape1 manages the HP 7974, HP 7978, and HP 7980 tape drives.

Hardware Paths

The hardware path in a devicefile specification is an arbitrary length string of numbers each suffixed by slash, ”/”, followed by an arbitrary length string of numbers separated by periods, ”.”. Each number identifies a hardware component. Hardware components suffixed by slashes indicate bus converters and may not be necessary on your machine. A single number is the shortest path specification. In w/x.y.z above, w would be the bus converter number, x would be the MID−BUS module number, y would be the CIO slot number, and z would be the HP−IB address or HP 27111 bus address.

Minor Numbers

The minor number, n, in a devicefile specification controls driver dependent functionality. The HP-UX System Administrator Manual describes the specific minor number encodings for the individual drivers. Since hpux manages its own logical units, it consequently ignores any logical unit information that may be specified in the minor number field of a devicefile. For more information on the minor number formats for disc0, disc2, disc1, lan1, and tape1 refer to the HP-UX System Administrator Manual.

Skip Counts

The skip count, s, in a devicefile specification controls how many files must be skipped before the desired file is reached. It is relative to the beginning of the tape, and is defined only for tape1 devices. It is ignored for all others. If not specified, 0 is assumed.

File Names

File names are standard HP−UX path names. No preceding slash (/) is necessary and specifying one will cause no problems. File names are not root (i.e. /) relative. For example, with disc0,disc1, and disc2, they are relative to the section specified in the minor number (in the device part) of the devicefile specification.

BOOT

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.

The default devicefile for boot has a minor number and skip count of zero, and a file name of hp−ux. The hardware path and manager are derived from the Primary Boot Path maintained by pdc(1M) or interactively given to pdc. For example, if pdc loaded isl from a CIO channel at MID−BUS module 8, the HP-IB card at CIO slot 0, and the CS−80 disc at address 0, the default devicefile would be disc0(8.0.0;0)hp−ux. For more details, consult the appropriate HP 9000 Series 800 architecture document.

Any missing components in a specified devicefile are supplied from the default above. For example, a devicefile of vmunix.new would actually yield disc0(8.0.0;0)vmunix.new and a devicefile of (8.0.1)hp−ux, for booting from the disc at HP−IB address 1, would yield disc0(8.0.1;0)hp−ux. 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.

The boot operation accepts several options. Their meanings are:

−a devicefile
This option takes a devicefile specification (see DEVICEFILES) and passes it to the loaded image. If that image is an hp−ux kernel, the kernel will erase its predefined I/O configuration, and configure in the specified devicefile. Note that the use of −a implies the −o option.

−fnumber This option takes a number (see NUMBERS) and passes it as the flags word to the loaded image.

−istring This option accepts a string that specifies the initial run−level for init(1M). Note that the run−level specified will override any run−level specified in an initdefault entry in /etc/inittab (see inittab(4)).

−o This option passes the console and boot device paths and drivers to the loaded image. If that image is an hp−ux kernel, the kernel will erase its predefined I/O configuration, and replace its console and root device paths and drivers with those passed from boot. In addition, the primary swap device is also placed on the boot device. This is useful for forcing a boot if the kernel has an incorrect I/O configuration.

−r This option is not currently supported. It was previously used as a debugging tool.

−m[p|s] If the loaded image is an hp−ux kernel, this option controls the kernel’s choice of which section in a mirrored root should be ONLINE. Without this option, the kernel chooses the section that was ONLINE when the system went down, or the primary section if both sections were ONLINE. −m alone causes the kernel to use the previously OFFLINE section, or the secondary section if both sections were previously ONLINE. −mp and −ms specify the primary and secondary sections, respectively.

Boot currently places some minor restrictions on object files it can load. It accepts only the HP−UX magic numbers SHAREMAGIC (0410) and DEMANDMAGIC (0413) (see magic(4)). The object file must contain an Auxiliary Header of the HPUX_AUX_ID type and it must be the first Auxiliary Header (see a.out(4)).

INSTALL

The install operation is used during first−time installation to load and execute an install image from a properly formatted installation device. The install operation is automatically translated to a boot operation from a devicefile based on the model of your system. The path to the install source device is the same as the one specified to pdc.

COPY

The copy operation is obsolete and should not be used. It was originally used during first−time installation to copy installation images from one device to another. Using this operation may damage your file system.

LS

The ls operation lists the contents of the HP−UX directory specified by the optional devicefile. The output is similar to that of the ls -alFH command, except that the owner, group, and date information is not printed.

The default devicefile for ls is generated in the same way as the devicefile for boot. However, the default file name is “.”.

EXAMPLES

Before going over specific examples of the various options and operations of hpux, here is an outline of the steps taken in the automatic boot process. Although the hardware configuration and boot paths shown are for a single Series 800 machine, the user interfaces are consistent across all models. When the system RESET button is depressed, pdc executes self−test, and assuming the hardware passes, pdc announces itself, issues a BELL, and gives the user 10 seconds to override the autoboot sequence, by entering any character. The following is typically displayed on the console.

Processor Dependent Code (PDC) revision 2

Console path = 8.1.0.0.0.0.0 Primary boot path = 8.0.0.0.0.0.0 Alternate boot path = 8.2.3.0.0.0.0

Autoboot from primary boot path enabled. To override, press any key within 10 seconds.

If no character is entered within 10 seconds, pdc commences the autoboot sequence by loading isl and transferring control to it. Because an autoboot sequence is occurring, isl merely announces itself, finds and executes the autoexecute file which, on an HP−UX system, requests that hpux be run with appropriate arguments. The following is displayed on the console.

10 seconds expired.

Booting.

Console IO Dependent Code (IODC) revision 1 Boot IO Dependent Code (IODC) revision 1

Booted.

ISL Revision 2634 August, 1986

ISL booting hpux

Next hpux announces the operation it is performing, in this case boot, the devicefile from which the load image comes, and the TEXT size, DATA size, BSS size, and start address of the load image. The following is displayed before control is passed to the image.

Boot : disc0(8.0.0;0x0)hp−ux 966616+397312+409688 start 0x6c50

Lastly, the loaded image, in this case an HP−UX operating system kernel, starts by giving numerous configuration and status messages. The system in the following example eventually comes to init run−level 2 for multi−user mode of operation.

Beginning I/O System Configuration.
cio_ca0 address = 8
   hpib0 address = 0
      disc0 lu = 0 address = 0
      disc0 lu = 1 address = 1
      disc0 lu = 2 address = 2
      disc0 lu = 3 address = 3
   mux0 lu = 0 address = 1
      .
      .
   [More deleted for brevity]
      .
      .
graph0 lu 0 address 12
I/O System Configuration complete.
Configure called
@(#)9245XA HP−UX (sys.A.B1.10/S800) #1: Wed Dec 10 17:24:28 PST 1986
real mem = 8386560
lockable mem = 3297280
avail mem = 5197824
using 204 buffers containing 837632 bytes of memory

In order to use the operations and options of hpux, isl must be brought up in interactive mode. To do this simply enter a character during the 10 second interval allowed by pdc. Pdc will then ask if the primary boot path is acceptable. Answering yes (Y) is usually appropriate. Pdc will then load isl and isl will interactively prompt for commands. The following is displayed.

Boot from primary boot path (Y or N)?> Y

Booting.

Console IO Dependent Code (IODC) revision 1 Boot IO Dependent Code (IODC) revision 1

Booted.

ISL Revision 2634 August, 1986

ISL>

Although all the operations and options of hpux may be used from isl interactively, they may also be executed from an autoexecute file. Refer to the appropriate documentation for building autoexecute files. In the examples below, all user input is in boldface type.

Default Boot

ISL> hpux

Boot : disc0(8.0.0;0x0)hp−ux 966616+397312+409688 start 0x6c50

Entering hpux initiates the default boot sequence. The boot path read from pdc is 8.0.0, the manager associated with the device at that path is disc0, the minor number is 0 specifying section 0 of the disc, and the object file name is hp−ux.

Booting Another Kernel

ISL> hpux vmunix.new

Boot : disc0(8.0.0;0x0)vmunix.new 966616+397312+409688 start 0x6c50

Here hpux initiates a boot operation where the name of the object file is vmunix.new.

Booting from Another Section

ISL> hpux (;3)sys.azure/S800/vmunix

Boot : disc0(8.0.0;0x3)sys.azure/S800/vmunix 966616+397312+409688 start 0x6c50

In this example, a kernel is booted from another section of the root disc. For example, let’s say that kernel development takes place under /mnt/azure/root.port which happens to reside in its own section, section 3 of the root (i.e. default boot) disc. By specifying a minor number of 3, in the above example, the object file sys.azure/S800/vmunix is loaded from /mnt/azure/root.port.

Booting from Cartridge Tape

ISL> hpux (;4194336)hp-ux

Boot : disc0(8.0.0;0x400020)hp-ux 966616+397312+409688 start 0x6c50

In this example, the default boot device is an HP 7914 disc with a cartridge tape at unit 1. The minor number has the cartridge tape flag set and specifies unit 1, section 0 of the device. Although the minor number was entered in decimal format, the hexadecimal form would be accepted. Since a file name is specified, it is assumed that section 0 contains a file system.

Booting from Another Disc

ISL> hpux (8.0.1)hp-ux

Boot : disc0(8.0.1;0x0)hp-ux 966616+397312+409688 start 0x6c50

In this example, only the hardware path is specified. All other values are boot defaults. The object file comes from the file system in section 0 of the disc, at HP−IB address 1.

Booting from LAN

ISL> hpux lan1(32)hp-ux

Boot : lan1(32;0x0)hp-ux 966616+397312+409688 start 0x6c50

This example shows how to boot a diskless client from the LAN. Though this example specifies a devicefile, using default boot, shown in a previous example, is also possible. For a boot operation other than default boot, the file name must be specified and be no more than 11 characters in length. Booting to isl from a local disk and then requesting an image to be loaded from the LAN is NOT supported.

Booting from a Raw Device

ISL> hpux tape1(8.2.3;0xa0000,1)

Boot : tape1(8.2.3;0xa0000,1) rewinding tape1(8.2.3;0xa0000,1) ... done skipping 1 file ... done 966616+397312+409688 start 0x6c50

This example shows booting from a raw device (i.e. no file system is on the device). Note that no file name is specified in the devicefile. The device is an HP 7974 tape drive and therefore tape1 is the manager used. The tape drive is at CIO slot 2, HP−IB address 3. The first file on the tape will be skipped. The minor number specifies a tape density of 1600 BPI and no rewind on close. Note that, depending on the minor number, tape1 requires the tape be written with 512 or 1024 byte blocks.

Booting to Single User Mode

ISL> hpux -is

Boot : disc0(8.0.0;0x0)hp-ux 966616+397312+409688 start 0x6c50

Kernel Startup Messages Omitted

INIT: Overriding default level with level ’s’

INIT: SINGLE USER MODE WARNING: YOU ARE SUPERUSER !!

#

In this example, the −i option is used to make the system come up in run−level s, for single user mode of operation.

Booting with a Modified I/O Configuration

ISL> hpux -a tape1(8.2.0)

Boot : disc0(8.0.0;0x0)hp-ux : Adding tape1(8.2.0;0x0)... 966616+397312+409688 start 0x6c50 Beginning I/O System Configuration. cio_ca0 address = 8
   hpib0 address = 0
      disc0 lu = 0 address = 0
   mux0 lu = 0 address = 1
   hpib0 address = 2
      tape1 lu = 0 address = 0 I/O System Configuration complete.

Additional Kernel Startup Messages Omitted

Here a tape driver is configured in at CIO slot 2, HP-IB address 0. Regardless of what was present in the kernel’s original I/O configuration, the driver tape1 is now configured at that hardware path. The only other devices configured are the console and root device, which boot derived from pdc .

First−Time Installation

ISL> hpux install

Boot : tape1(8.2.3;0xa0000,1) rewinding tape1(8.2.3;0xa0000,1) ... done skipping 1 file ... done 966616+397312+409688 start 0x6c50

This is an example of the install operation on a model 840. In this example, pdc was instructed to boot from the boot path, "8.2.3". hpux translated the install operation to a boot operation from this boot path using defaults characteristic of the model 840. As a general rule, smaller systems (for example, model 815) will default to installing from cartridge tape while larger systems (for example, model 850) default to reel tape.

Listing Directory Contents

ISL> hpux ls

Ls : disc0(8.0.0;0x0).

—

2048 ./

—

2048 ../

—

4096 lost+found/

—

746 .profile

—

1024 bin/

—

1024 dev/

—

1024 etc/

64 tmp/

—

1024 usr/

—

884736 hp-ux*

—

884736 SYSBCKUP*

—

1032192 hp-ux.test*

The contents of the root directory (/) on the root disc are listed. The format shows the file protections, number of links, and size in bytes for each file in the directory. There are three available kernels to boot: hp−ux, hp−ux.test, and SYSBCKUP. Listing the files of a diskless server from a diskless client is not supported.

Getting the Version

ISL> hpux -v
Release: 1.1
Release Version:
@(#)9245XA HP−UX (sys.A.B1.10/HPUXBOOT) #1: Wed Dec 10 17:24:28 PST 1986

The −v option is used to get the version numbers of hpux.

DIAGNOSTICS

In the instance of an error hpux prints diagnostic messages which indicate the cause of the error. These messages may be grouped General, Boot, Copy, Configuration, and System Call. A description of the System Call error messages may be found in errno(2). The remaining messages are described below.

General

bad minor number in devicefile spec
The minor number in the devicefile specification is illegal.

bad path in devicefile spec
The hardware path in the devicefile specification is illegal.

command too complex for parsing
The command line contains too many arguments.

no path in devicefile spec
The devicefile specification does not contain a hardware path component and must.

panic (in hpuxboot): (display==number, flags==number) string
A severe internal hpux error has occurred. Report to your nearest HP Field Representative.

Boot

bad magic
The specified object file does not have a legal magic number.

bad number in flags spec
The flags specification in the −f option is illegal.

booting from raw character device
In booting from a raw device, the manager specified only has a character interface. This may cause problems if the block size is incorrect.

Isl not present, please hit system RESET button to continue
An unsuccessful boot operation has overlaid isl in memory. It is impossible to return control to isl.

short read
The specified object file is internally inconsistent, it is not long enough.

would overlay
Loading the specified object file would overlay hpux.

Copy

cannot open destination device/file
The destination device or file could not be opened for writing.

cannot open source device/file
The source device or file could not be opened for reading.

fchmod failure (warning only)
The access mode of the destination file could not be changed.

fchown failure (warning only)
The owner and/or group of the destination file could not be changed.

fstat failure (warning only)
One or more of the owner, group, or mode of the source file could not be determined. The default values of owner and group are 0 and 0. The default mode is 0777.

read failure
An error was encountered reading from the source device or file.

umount failure on destination device
The destination device could not be dismounted. Its file system may have been damaged as a result. Fsck should be run before mounting the file system.

umount failure on source device
The source device could not be dismounted. Since it was mounted read−only, the integrity of its file system is not at risk.

write failure
An error was encountered writing to the destination device or file.

Configuration

cannot add path, error number
An unknown error has occurred in adding the hardware path to the I/O tree. The internal error number is given. Contact your HP Field Representative.

driver does not exist
The manager specified is not configured into hpux.

driver is not a logical device manager
The manager name given is not that of a logical device manager and cannot be used for direct I/O operations.

error rewinding device
An error was encountered attempting to rewind a device.

error skipping file
An error was encountered attempting to forward−space a tape device.

negative skip count
The skip count, if specified, must be greater than or equal to zero.

no major number
The specified manager has no entry in the block or character device switch tables.

path incompatible with another path
Multiple incompatible hardware pathes have been specified.

path long
The hardware path specified contains too many components for the specified manager.

path short
The hardware path specified contains too few components for the specified manager.

table full
Too many devices have been specified to hpux.

Museum

Related Articles