instl_adm.4 (2012 03)

i
instl_adm(4) instl_adm(4)
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) ser-
vice 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:
• Within a sw_source definition.
• Within a sw_sel definition.
• At the global level.
Although only the
= assignment operator is shown with these keywords, the
+= operator can also be
used to add a script or command fragment to any existing assignments made to the same keyword in the
same context. The
= operator overwrites any prior assignments made for that keyword. A separate con-
text for each keyword is kept for the global level, each unique sw_source and each unique sw_sel
.
The exit code returned by a script results in different handling by the Ignite-UX installation process:
0 Ignite-UX does not display any additional messages and proceeds
1 Ignite-UX displays an additional ERROR message and proceeds
2 Ignite-UX displays an additional WARNING message and proceeds
4 Ignite-UX displays an additional ERROR message and terminates
other
The results are undefined
The point in time that the associated commands or scripts are executed is described below.
pre_load_cmd = cplx_string
pre_load_script = cplx_string
The global
pre_load commands and scripts are executed prior to any software installation, and
after the file systems have been created. Those within a sw_source or a sw_sel definition are
executed prior to loading any software from the respective source. Those associated with a
sw_source are executed before of any associated with a sw_sel.
post_load_cmd = cplx_string
post_load_script =
cplx_string
The global
post_load commands and scripts are executed after all software has been installed,
but prior to the final client reboot, and software configuration step. Those within a sw_source or
sw_sel definition are executed after all software from the associated source has been installed and
prior to the global post_load commands and scripts. Those associated with a sw_sel are exe-
cuted ahead of any associated with a sw_source (opposite order of pre_load). This is the
correct hook to use if customizations to the kernel via the /stand/system
file are to be made
beyond what is capable through the
mod_kernel keyword.
post_config_cmd = cplx_string
post_config_script = cplx_string
The post_config commands and scripts are executed after all software has been configured and
the final client kernel has been built and booted. It is safe to execute commands in this environment
that may have dependencies on the version or modifications of the kernel that was put into place
prior to rebooting. The post_config commands and scripts associated with a sw_source or
sw_sel are executed first, and then the global versions last.
Note that if
is_net_info_temporary is true, then certain commands are not usable at this
time. If it is true, then certain networking files (e.g. etc/hosts) are gone, and so commands like
swconfig do not work.
HP-UX 11i Version 3: March 2012 − 31 − Hewlett-Packard Company 31