_hp_os_bitness

The _hp_os_bitness string variable is used to package software for running on a 32-bit operating system, 64-bit operating system, or both. The _hp_os_bitness variable is set to either 32 or 64 when an operating system is chosen. This is normally done in a configuration file by keying off the sw_sel for a 32- or 64-bit operating system. The sw_sel statements for certain applications rely on the setting of this variable to tell which version of the application to install.

This variable is set by the core operating system sw_sel that was selected, for example:

sw_sel "HPUXBase64" {

description = "HP-UX 64-bit Base OS"

...

}

(sw_sel "HPUXBase64") { _hp_os_bitness = "64"

}

When the software HPUXBase64 is selected (so the test "(sw_sel "HPUXBase64")" returns true) the variable _hp_os_bitness is set to 64. The make_config command automatically does this for you. However, if you manually write configuration files containing definitions of a core operating system depot or archive, you must set this variable to the correct bitness.

_hp_force_autoboot

The _hp_force_autoboot string variable is used to modify the behavior of Ignite-UX with respect to stable store's autoboot flag. The Ignite-UX configuration process has two parts separated by a reboot. By default (_hp_force_autoboot="YES"), Ignite-UX guarantees that autoboot is set during the installation process and then reset to its previous state (if necessary) at the end of the installation. If _hp_force_autoboot="NO", Ignite-UX does not modify the autoboot flag in stable storage. This may mean that you do not have to do a manual boot from the primary path between the two parts of the Ignite-UX installation.

Ignite-UX normally forces the system to perform the first reboot automatically when rebooting from the installation kernel to the newly created or recovered kernel. This reboot is forced no matter what the autoboot flag is set to (refer to setboot(1M)). Ignite-UX forces it on if it was off; prior to the final reboot Ignite-UX returns the autoboot flag to off. If _hp_force_autoboot is set to NO and the system’s autoboot flag is set to off, the system cannot complete the recovery and boot the final recovered or installed system, which leaves the system at the BCH, prompt.

Important:

If you disable autoboot and then install a system, the system never executes a final reboot without manual intervention. HP does not support booting into any other mode than the default multi-user run level at this point. The installation or recovery session has not yet completed and some steps must still be performed by Ignite-UX. Booting into anything other than the default run level does not allow the installation or recovery to complete. This is the intended behavior of Ignite-UX and not a flaw. In general (except when investigating Ignite-UX issues on advice from HP Support), you should never change the value of the _hp_force_autoboot variable.

101