Ignite-UX Administration Guide for HP-UX 11i (B3921-90079, October 2013)

How the Installation Functions
It is important to understand how an installation functions when using Ignite-UX. The diagram in
Figure 95 illustrates when the various commands and scripts are executed during the installation
process.
Figure 95 Installation Process
Install kernel
boots
pre_config_cmd
pre_load_[cmd|script]
post_load_[cmd|script]
Pre-software
load
Software load
(archive or
depot)
Software and
system
configuration
post_config_[cmd|script]
final_[cmd|script]
OS archive
loaded
Additional
software
Kernel
creation
Reboot on
new kernel
Software
configured
Final
reboot
1
2
3
1 The commands available are very limited and execute before any volume groups or disk groups
are created.
2 The available preload commands are limited and the script executes before any archives or
depot-based software are installed.
3 The install.log file is closed, then the final scripts execute; any messages that are generated
appear only on the console.
There are a number of points in the installation process in which you can force scripts or commands
to be run. See the "Command and Script Execution Hooks" section of instl_adm(4) for specifics.
Adding a Post-Installation Script
Example
One task you generally need to perform after a new operating system installation is setting up
printers. To automate this process, you can write a script that performs the HP-UX commands for
adding a printer.
Following is a script for adding a remote printer named remoteprinter, making it the default
printer, and then enabling the printer so that it is ready the next time that the lp scheduler is started:
#!/usr/bin/sh
# Post process IUX script to add a local default printer
Using Post-Installation Scripts 169