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

instl_adm(4) instl_adm(4)
load_with_any ˜ tag-reg exp [[ | tag-reg exp ]...]
load_with_any ˜ category.tag-reg exp ...
Specifies that when the ˜ operator is used rather than =, the sw_sel tags listed are
treated as fnmatch(3C) regular expressions that may be used to match any selection fitting
the given pattern. Note this operator uses fnmatch(3C) pattern matching expressions.
Other uses of the ˜ operator in the configuration file are with extended regular expres-
sions. This difference is for compatibility with some existing data. The category string
may be specified, with a "." separator, to limit matches to those selections in the specified
software category.
load_with_all = tag_string [[ & tag_string ]...]
Specifies that when all the sw_sels listed are selected, this sw_sel is selected as well.
Multiple tags may be listed separated by the & character.
If multiple load_with_* keywords are specified, the list of tag strings is added to any
already listed for the respective keyword.
also_select = tag_string [[ | tag_string]...]
also_select ˜ tag-reg exp [[ | tag-reg exp ]...]
also_select ˜ category.tag-reg exp ...
The also_select keyword allows for one sw_sel to effect the selection of other
sw_sels. It is different than a corequisite in that software selected (or unselected)
by this mechanism can be individually unselected (or selected) without effecting the
selection status of the referencing sw_sel. In contrast, a corequisite cannot be
unselected if the item declaring the corequisite is selected.
When selecting (setting to true) a sw_sel ("A") that declares an also_select on
another sw_sel ("B"), the sw_sel "B" will also be selected. Similarly, when
sw_sel "A" is unselected, then sw_sel "B" will also be unselected.
The argument syntax of this keyword is the same as the load_with_any keyword.
pre_load_cmd = cplx_string
post_load_cmd = cplx_string
post_config_cmd = cplx_string
final_cmd = cplx_string
Specify a shell command string that should be executed at the prescribed points during
the installation when this sw_sel has been selected. See the Command and Script
Execution Hooks section for details.
pre_load_script = cplx_string
post_load_script = cplx_string
post_config_script = cplx_string
final_script = cplx_string
Specify a shell script that should be loaded from the Ignite-UX server using tftp and
executed at the prescribed points during the installation if this sw_sel is selected. See
the Command and Script Execution Hooks section for details.
Command and Script Execution Hooks
Ignite-UX supports mechanisms for the commands and scripts you supply to be inserted into various stages
in the installation process. There are two types of keywords that the configuration file supports. The
keywords that end in _cmd may be used to embed scripts directly in the configuration file. This is useful
when the command desired to be executed is short and may be inserted directly into the configuration file
without compromising the maintainability of the configuration file. The keywords that end in _script
are used to reference files to be loaded from the Ignite-UX server using the tftp(1) service and executed as a
stand-alone command.
With the exception of the pre_config_cmd keyword, the execution hooks may be specified in three
different areas of the configuration file. These areas are:
34