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

instl_adm(4) instl_adm(4)
execute commands in this environment that may have dependencies on the version or modifica-
tions of the kernel that was put into place prior to rebooting. The final commands and scripts
associated with a sw_source or sw_sel are executed first and the global versions last.
Note that if a temporary host name/IP address is used during the installation, all the commands
and scripts, including the final_cmd/script, are executed while that temporary information is
in effect. If you require the final networking information to be in effect, then you may need to
have it run at the first client boot by loading the script in the /sbin/rc*.d directory and hav-
ing it remove itself when completed.
pre_config_cmd = cplx_string
A list of semicolon separated commands can be set to execute prior to the creation and mounting
of file systems. It also runs prior to the Ignite-UX UI. There are almost no commands available at
this stage; not even a shell. Any commands needed have to be loaded by using the loadfile
command that exists in this environment. For command usage, type "loadfile -?" from a recovery
shell.
It is inadvisable to do any sort of software loading via invoking swinstall directly from any command
or script hook. This can lead to various problems such as missing disk space impacts, ensuring the software
is fully configured, and getting kernel software loaded before the kernel is built. It is much better to use the
standard software mechanisms provided with the sw_source and sw_sel attributes as required. Fur-
thermore Ignite-UX exports environment variables that control swinstall behavior, and this can have
unexpected results.
In addition to the hooks above that may be specified in an Ignite-UX configuration file, Ignite-UX provides
a way for applications that are installed using an archive to supply scripts to be run. After installing any
software from an archive, Ignite-UX recursively searches the /var/adm/sw/products directory for
any scripts entitled iux_postload and iux_postconfig.Anyiux_postload scripts provided
by the archive(s) are run after all software sources are installed and before the client kernel is built. Any
iux_postconfig scripts found are run after all software is installed and the system is running on the
final kernel. The order is similar to the post_load_cmd and post_config_cmd keywords described
previously . These scripts are not executed if they were installed from an SD depot, because the regular SD
control scripts are run.
When Ignite-UX is provided with a final system host name, it searches the /sbin/ch_hostname.d
directory, if it exists, for any executable files/scripts. It then runs the executables in that directory with a
single argument of the new host name. Note that this host name argument may be different than the one
currently in use, and takes effect after the pending reboot. The scripts are run in the order in which the ls
command sorts them. This hook may be useful for products that need to modify configuration files based
on the host name and would normally do this in an SD configure script. A recommendation for software
product developers is that any host name specific tasks be done using this hook, and that the SD control
script call the script in this directory as well. Note that SD configure scripts are not run when using Ignite-
UX to install a client from a client archive. The scripts in /sbin/ch_hostname.d must be re-
runnable any time the host name changes. In the HP-UX B.11.11 release, the set_parms command will
also implement this mechanism to be used on initial system setup, as well as, host name changes.
When a tar/cpio/pax archive is used to supply the core HP-UX operating system (a full system
archive), you should to use the two scripts that are supplied with Ignite-UX. These scripts should be asso-
ciated with the sw_sel that references the system archive. See the example configuration file,
/opt/ignite/data/examples/core.cfg. There is one post_load_script,
/opt/ignite/data/scripts/os_arch_post_l, and one post_config_script,
/opt/ignite/data/scripts/os_arch_post_c. These shell scripts may require customizations
to meet your needs. See the comments provided in the files for more details.
Configuration File Parsing Order and Precedence
In general, the configuration files are parsed in the order that they are listed in the INDEX file cfg state-
ment selected. In addition, the information stored in the first 8KB of the *INSTALLFS file and the file
entitled
config in the client-specific directory are parsed after those listed in the INDEX file.
36