NAME
bootconf — boot device configuration table
DESCRIPTION
The
/stand/bootconf
file contains the address and disk layout type of the system's
boot devices or
lif
volumes.
It is used by the
Software Distributor
and HP-UX kernel control scripts
(fileset
OS-Core.KERN-RUN)
to determine how and where to update the initial boot loader.
Normally the kernel's
checkinstall
script queries the system's hardware and creates the file.
In rare cases when either the system configuration cannot be
automatically determined or additional and/or alternate boot devices
should be automatically updated, the administrator must
edit the
/stand/bootconf
file manually.
There is one line in the file for each boot device.
Each line contains the
following blank-separated fields in the order shown:
- disk type
A flag indicating how the file system(s) on the disk are laid out.
The flag must be one of the following:
- l
Indicates that the root disk is in LVM or VERITAS Volume Manager
(VxVM) format.
If LVM or VxVM mirrors are used, then each of the "mirrors" must
have its own line in the file.
- w
Indicates that the root disk is in the
"whole disk" format with no partitions, but boot and swap
space are reserved outside the file system.
- device file
The absolute path of the device special file that accesses the physical
device where the boot area is located.
For LVM root disks, the device special file is
the physical volume(s) returned by the
vgdisplay -v
command.
For "whole disks" this
is the device file that references the entire disk.
Blank lines are permitted.
Any line beginning with a
#
is considered to be a comment.
DIAGNOSTICS
The Software Distributor log file
/var/adm/sw/swagent.log
contains diagnostic messages under the
OS-Core.KERN-RUN
fileset if the
bootconf
file is incorrect.
Most of the messages are self-explanatory;
a few warrant additional explanation:
- ... is either empty or improperly formatted...
If there are no other messages about
bootconf,
the file is probably empty.
Otherwise, the file is not in the proper
format, and the other messages will explain what the problem is.
- device file ... does not contain a valid boot LIF ...
The specified device file does not point to a disk where there is a
lif
which contains the file
HPUX.
- ... has an invalid character in the flag field...
Some character other than
#,
l,
or
w
is in the first field of a line.
- ... contains contradictory boot LIF types...
As of release 10.0, the boot areas in
/stand/bootconf
must all be on the same type of disk layout.
- ... has unrecognized extra characters...
There are characters after the
device file
specification.
EXAMPLES
The boot area is on an LVM root disk:
The boot area is on a whole disk layout:
WARNINGS
All of the boot devices in the file must have the same disk layout.
AUTHOR
bootconf
was developed by the Hewlett-Packard Company.
Printable version
