–koption, enables you to specify an alternate file to read. Refer to keymap_ed(1) for more information.

The standard configuration files use _hp_keyboard visible_if false to prevent this variable from being visible or changeable using the Additional button in the Ignite-UX GUI. It can be set for clients with required hardware from the Keyboard button on the Basic tab. If the hardware is not present, the only choice presented is "Not Applicable". If "Not Applicable" is chosen or left as a default, then the keyboard language/mapping is prompted for when the system boots the first time if the system has a graphics console and keyboard attached.

_hp_root_disk

The _hp_root_disk string variable is set by the Ignite-UX GUI to contain the hardware path of the disk that the user has chosen to be the root disk. The value is initialized to the value of _hp_primary_path in /opt/ignite/data/Rel_*/config, and can be overridden in other config files. If no config file were to set the initial value, then it would default to the disk with the hardware path with the highest SCSI priority.

The standard installation configuration attempts to set the variable _hp_root_disk to the value of _hp_primary_path if _hp_primary_path is set. The variable _hp_primary_path holds the hardware path to the disk that the system is set up to boot from by default (set by setboot or selected at the BCH56 prompt). If the primary path setup for the system points to a nonexistent device, _hp_root_disk is not be set by this configuration. Instead, Ignite-UX chooses what it determines to be the "best" device for the variable instead.

(_hp_primary_path != "" & !(_hp_root_disk ~ ".*"))

{

init _hp_root_disk=_hp_primary_path

}

During an interactive installation or recovery, you can modify this value using the Ignite-UX GUI using the Root Disk… button on the Basic tab to get a selection of choices. It can also be changed using the File system tab in Add/Remove Disks… dialog box by changing the disks that are assigned to root volume or disk group. However, in the Add/Remove Disks… dialog box Ignite-UX chooses which of the disks (if more than one) is assigned to _hp_root_disk (initially anyway, after that they can be modified).

The standard configuration files use _hp_root_disk visible_if false to prevent this variable from being from visible or changeable using the Additional button in the Ignite-UX GUI.

_hp_boot_dev_path

The variable _hp_boot_dev_path is not defined by instl_adm(4). Do not rely on this description and the behavior defined here because they may change without notice.

If bootsys was used on a disk that was not destroyed during the installation, then the disk has an AUTO file left over from bootsys. Typically, you want to be able to boot from that disk after the installation is done. The disk that you booted from originally is pointed to by _hp_boot_dev_path.

56Boot Console Handler: the firmware boot prompt on PA-RISC systems.

92