Ignite-LUX: Management and Integration of Ignite-UX Software on a Server Running Linux

26
Files may also be located on the Ignite-UX server and accessed via NFS so that they do not need to be
included in installed content. For example:
post_config_script += "/usr/contrib/bin/gunzip \
/var/opt/ignite/data/CMS_agent.tar.gz | tar xvf -"
Note that Ignite-UX includes several of these hooks at different phases in the installation process. In the
earlier stages, only very limited HP-UX commands are available. When possible, this type of customization
should be done in the late stages, as in the example above. See instl_adm(4) for more information.
It is also possible to have the INDEX configuration clause include content from a depot on an HP-UX server.
In this case the configuration clause may include a golden image and a depot. The depot must come from
an HP-UX Software Distributor server.
Installing Additional HP-UX OS Software and Patches
It might be desirable to install additional HP-UX software as part of the initial system installation or after
installation has completed. HP-UX OS software is packaged in Software Distributor depot format. During
initial network installation, support of installation of this software will require an Ignite-UX server that is
distinct from the Ignite-LUX server.
Another alternative is to use CMS agent control or HP-UX scripts during boot-after-install to install additional
software. HP-UX Software Depot commands may be used to convert depots to a serial format consisting of a
single file. A serial depot may be located on the Ignite-LUX server and accessed via NFS.
Warning: Do not use Ignite-UX config file program or command hooks to attempt swinstall. This will
result in overlapping installations and unpredictable results. In some cases installation might work or might
appear to work, but you cannot be confident in the results. Ignite-UX installation should be allowed to fully
complete before additional software is installed.