mkboot.1m (2010 09)
m
mkboot(1M) mkboot(1M)
options. This option will also fail on a disk having large-file enabled HFS
filesystem.
device Install the boot programs on the given device special file. The specified
device can identify either a character-special or block-special device.
However,
mkboot requires that both the block and character device spe-
cial files be present. mkboot attempts to determine whether device is
character or block special by examining the specified path name. For this
reason, the complete path name must be supplied. If
mkboot is unable to
determine the corresponding device file, a message is written to the
display, and
mkboot exits.
rmboot removes the boot programs from the boot area.
EXAMPLES
Install default boot programs on the specified disk, treating it as an LVM disk:
mkboot -l /dev/dsk/c0t5d0
Use the existing layout, and install only SYSLIB and ODE files and preserve the EST file on the disk:
mkboot -i SYSLIB -i ODE -p EST /dev/rdsk/c0t5d0
Install only the SYSLIB file and retain the ODE file on the disk. Use the Whole Disk layout. Use the file
/tmp/bootlf to get the boot programs rather than the default. (The -i ODE option will be ignored):
mkboot -b /tmp/bootlf -i SYSLIB -i ODE -p ODE -W /dev/rdsk/c0t5d0
Install EFI utilities to the EFI partition on an Itanium-based system, treating it as an LVM or VxVM disk:
mkboot -e -l /dev/dsk/c3t1d0
Create AUTO file with the string autofile command on a device. If the device is on an Itanium-based
system, the file is created as /EFI/HPUX/AUTO
in the EFI partition. If the device is on a PA-RISC sys-
tem, the file is created as a LIF file in the boot area.
mkboot -a "autofile command" /dev/dsk/c2t0d0
WARNINGS
If device has a Whole Disk layout, a file system must reside on the device being modified.
When executing from a recovery system, the
mkboot command (if used) must be invoked with the -f
option; otherwise it will not be able to replace the boot area on your disk.
If device is, or is intended to become an LVM physical volume, device must specify the whole disk.
If device is, or is intended to become a Hard Partitioned disk, device must specify section 6.
If you receive a message that says "statvfsdev: Can’t send after socket shutdown", check with your system
administrator to make sure the
fsdaemon is running properly on your system.
DEPENDENCIES
mkboot and rmboot fail if file system type on device is not HFS.
LVM and Hard Partition Layouts
The
-f, -h, and -u options are not supported.
AUTHOR
mkboot and rmboot were developed by HP.
FILES
/usr/lib/uxbootlf file containing default PA-RISC boot programs
/usr/lib/efi file containing default Itanium-based system (EFI) boot programs
ISL initial system loader
HPUX HP-UX bootstrap and installation utility
AUTO defines default/automatic boot behavior (see hpux(1M))
LABEL used by LVM
RDB diagnostics tool
IOMAP diagnostics tool
HP-UX 11i Version 3: September 2010 − 3 − Hewlett-Packard Company 3