It is important to understand how an installation functions when using
Figure 97 Installation process
Install kernel |
|
| pre_config_cmd |
| ||||
boots |
|
| pre_load_[cmdscript] | load | 1 | |||
|
| |||||||
|
|
|
|
|
|
|
| |
|
|
|
|
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
OS archive |
|
|
|
|
| |||
loaded |
|
|
|
|
| |||
|
|
|
|
|
|
| Software load |
|
|
|
|
|
|
|
|
| |
Additional |
|
|
|
| ||||
|
|
| (archive or |
| ||||
software |
|
|
|
| ||||
|
|
| depot) | 2 | ||||
|
|
|
|
|
| post_load_[cmdscript] | ||
|
|
|
|
|
|
|
| |
|
|
|
|
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Kernel |
|
|
|
|
| |||
creation |
|
|
|
|
| |||
|
|
|
|
|
|
|
|
|
Reboot on new kernel
Software |
|
|
|
| ||
configured |
|
| Software and |
| ||
|
|
|
| post_config_[cmdscript] | system |
|
|
|
|
| configuration | 3 | |
|
|
|
| final_[cmdscript] | ||
|
|
|
|
|
|
|
|
|
|
|
|
| |
Final |
|
|
|
| ||
reboot |
|
|
|
| ||
|
|
|
|
|
|
|
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
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 aExample
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
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
172 Customizing your installation