Ignite-UX Reference (March 2010, B3921-90005)

instl_adm(4) instl_adm(4)
_hp_saved_detail_level
Internal string variable used in configuration files that have been created by a "Save-As" operation.
Like _hp_cfg_detail_level, it contains a list of option characters that represent which
aspects of the configuration file have been modified. The format is identical to the
_hp_cfg_detail_level variable.
_hp_sec_swap
Integer variable that may be set in the UI to indicate how much secondary swap the user desires to
have allocated in the root volume-group. The default is zero (no secondary swap). If there is more
than one disk in the root volume group, this volume is mapped to the second disk.
_hp_tftp_cmds
String variable that may be specified in the *INSTALLFS file to supply additional instructions to
the tftp commands that are used to transfer data during an installation. The commands sup-
plied with this variable are passed as input to the tftp command along with the usual commands
supplied by Ignite-UX. The most likely use of this would be to modify the retransmission-timeout
(rexmt) and overall timeout (timeout) values. The default values that Ignite-UX uses are:
rexmt set to 2 and timeout set to 25. See tftp(1) for more details. The string assigned to this
variable should contain one tftp command statement per line. For example:
init _hp_tftp_cmds="rexmt 5
timeout 40"
Use Model Variables
The configuration file parser also supports an older version of variables that existed in previous releases.
These are referred to as use models. They are boolean variables in which the variable itself is a string and
its value is either true or false. The variable name is presented in the Additional dialog that is available in
the UI on the Basic tab. The user may toggle the boolean value.
Similar to variables, use models may be made invisible to the UI using the visible_if keyword.
Ignite-UX does not support the selectable_if or radio_sel keywords that previous releases sup-
ported. The radio_sel functionality is replaced by the ability for regular variables to have a list of pos-
sible values associated with them. Additionally, the help_text keyword for use models has no effect.
Use models use the same init keyword as regular variables. When a use model is assigned using the
init keyword, the UI is allowed to change that variable value. An example of how use models are used
is shown below:
init "use_model_name" = TRUE
init "use_model_name" = num_disks > 2
"use_model_name" visible_if (memory > 64MB)
Logic Expressions
A block of configuration statements may be surrounded by a logic expression and a set of {}brackets.
The logic expression may be made up of variables, use models or system attributes. The following logic
operators are recognized (in order of precedence):
() Parentheses may be used to group expressions to force precedence.
! Logical not operator.
== != ˜
Comparison operators: equal, not-equal and regular expression match, respectively. The == and
!= operators compare strings in a case-insensitive manner. The ˜ character is a regular expres-
sion comparison operator. The right side of ˜ is treated as an extended regular expression string
when compared to the left side string. (See regexp(5).)
><>=<=
Comparison operators: greater than, less than, greater or equal, and less or equal, respectively.
& Logical and operator.
9