mkboot.1m (2010 09)

m
mkboot(1M) mkboot(1M)
NAME
mkboot, rmboot - install, update or remove boot programs from disk
SYNOPSIS
/usr/sbin/mkboot
[-b boot_file_path ][-c [
-u]| -f | -h | -u][-i included_lif_file]
[
-p preserved_lif_file][
-l | -H | -W][
-v] device
/usr/sbin/mkboot
[-a auto_file_string ][-v] device
/usr/sbin/mkboot -e
[-l][-s efi_file_path ][
-v][-W] device
/usr/sbin/rmboot
device
DESCRIPTION
mkboot is used to install or update boot programs on the specified device file.
The position on device at which boot programs are installed depends on the disk layout of the device.
mkboot examines device to discover the current layout and uses this as the default. If the disk is unini-
tialized, the default is LVM layout on PA-RISC and Whole Disk on Itanium-based systems. The default
can be overridden by the
-l,
-H,or-W options.
Boot programs are stored in the boot area in Logical Interchange Format (LIF), which is similar to a file
system. For a device to be bootable, the LIF volume on that device must contain at least the
ISL (the ini-
tial system loader) and
HPUX (the HP-UX bootstrap utility) LIF files. If, in addition, the device is an
LVM physical volume, the LABEL file must be present (see lvlnboot (1M)).
For the VERITAS Volume Manager (VxVM) layout on the Itanium-based system architecture, the only
relevant LIF file is the
LABEL file. All other LIF files are ignored. VxVM uses the
LABEL file when the
system boots to determine the location of the root, stand, swap, and dump volumes.
Options
mkboot recognizes the following options:
-a auto_file_string If the
-a option is specified, mkboot creates an autoexecute file AUTO on
device , if none exists.
mkboot deposits auto_file_string in that file. If this
string contains spaces, it must be quoted so that it is a single parameter.
-b boot_file_path If this option is given, boot programs in the pathname specified by
boot_file_path are installed on the given device.
-c If this option is specified, mkboot checks if the available space on device
is sufficient for the boot programs. If the -i option is also specified,
mkboot checks if each included_lif_file is present in the boot programs. If
the
-p option is specified, it checks if each preserved_lif_file is present on
the device . If all these checks succeed,
mkboot exits with a status code of
0. If any of these checks fail, mkboot exits with a status code of 1. If the
verbose option is also selected, a message is also displayed on the stan-
dard output.
-e Use Itanium-based system EFI layout. This option causes mkboot to
copy EFI utilities from /usr/lib/efi to the EFI partition on the disk;
see idisk(1M) and efi(4). This option is applicable only on Itanium-based
machines; it may not be used on PA-RISC. (Use the -s option to specify
a non-default source for EFI files.)
-f This option forces the information contained in the boot programs to be
placed on the specified device without regard to the current swapping
status. Its intended use is to allow the boot area to grow without having to
boot the system twice (see -h option).
This option should only be used when the system is in the single user
state.
This could be a dangerous operation because swap space that is already
allocated and possibly in use will be overwritten by the new boot program
information. A message is also displayed to the standard output stating
that the operator should immediately reboot the system to avoid system
corruption and to reflect new information on the running system.
HP-UX 11i Version 3: September 2010 − 1 − Hewlett-Packard Company 1