Quick Start Guide

Glossary
Glossary terms are italicized when used for the first time in this manual and when used
anywhere in the glossary. This is a standard glossary for Ignite-UX documentation –
not all terms defined here appear in this guide.
A
add_new_client An Ignite-UX command that constructs a client directory on an Ignite-UX server without requiring
the client to be booted from the Ignite-UX server first. See add_new_client(1M).
agile addressing The ability to address a LUN with the same DSF regardless of the physical location of the LUN
or the number of paths leading to it. Agile addressing is introduced in HP-UX 11i v3.
agile view The representation of LUNs using lunpath hardware paths, LUN hardware paths, and persistent
DSFs, introduced in HP-UX 11i v3.
always-installed For HP-UX 11i v1 and 11i v2, the software and driver bundles required for HP-UX. They must
be loaded as part of the operating system.
anonymous client A client system that requests an IP address for booting when its MAC address is not associated
with a specific IP address on the server. An anonymous client has its IP address allocated from
a pool of IP addresses set aside for anonymous clients. See registered client.
ANSI tape label See standard label tape.
archive
1. A file made with make_sys_image that contains files for installation or recovery for a system.
The file format may be tar, cpio, or with HP-UX 11i v3, pax, and can be compressed. An
archive does not include file system or disk layout information. Archives can be either recovery
archives or golden archives. Recovery archives retain host-specific customizations from the system;
golden archives have customizable files reset to the newconfig state. An archive may include the
core HP-UX operating system, and may include application software, patches, and global
customizations. 2. A file containing the contents of other files, created and maintained by
programs such as pax, tar and cpio.
archive_impact An Ignite-UX command that calculates the disk space required for an archive on a per top level
directory basis by default. The results are written in Ignite-UX configuration file syntax to standard
output. See archive_impact(1M).
AUTO A file that defines default boot behavior. For PA-RISC systems, the AUTO file is in the LIF
volume. For Itanium®-based systems, the AUTO file is located in the /opt/ignite/boot
directory. See hpux(1M) and hpux.efi(1M).
auto_adm An Ignite-UX command that allows you to manipulate AUTO file contents. See auto_adm(1M).
automated
installation
Any installation done automatically, without manual interaction. This can be done at the
command line with a bootsys command, or it can be scheduled to run at a particular time using
the cron daemon.
B
Bastille A security hardening/lockdown tool that can enhance the security of the HP-UX operating
system. It provides customized lockdown on a system-by-system basis.
boot To load the kernel and start the operating system that is referenced by the kernel that was loaded.
See boot(1M).
boot console
handler (BCH)
The firmware interface on a PA-RISC system. The Itanium-based equivalent is the extensible
firmware interface.
boot content [W|V|I]INSTALL, [W|V|I]INSTALLFS, INSTCMDS or INSTCMDSIA, config files, and other files
to support boot and Ignite-UX functionality needed to switch to another install source.
boot helper media Installation media with no archive. Meant for booting only. Installation is completed using an
Ignite-UX server.
boot helper
system
A system with minimal Ignite-UX core functionality on a local subnet that provides an Ignite
install kernel to a client to assist it with booting from an Ignite-UX server on another subnet.
33