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

instl_adm(4) instl_adm(4)
• 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 context 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 executed 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 envi-
ronment 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.
final_cmd = cplx_string
final_script = cplx_string
The final commands and scripts are executed as the very last step before the final client reboot
or halt. In fact, these scripts and commands are executed after the log file has been closed and the
installation’s overall status has been determined. Thus, the exit code from a final_script
does not influence the outcome of the installation. Also, any information logged from these com-
mands and scripts is not written into the log file, but is written to the client console. It is safe to
35