Using an Initialization Script

Using an Initialization Script

The initialization script inst.init provides a means to delay an installation session until the appropriate session parameters are set by the script. The primary function of inst.init is to redirect a distribution specification to a different source, or to modify the default selections in a distribution. However, because an inst.init script can also include the use of selections files and set (preferences) commands, you can customize the script to meet a variety of installation requirements. The activation of inst.init is specified by the startup_script variable (see Table 8-1 for a description of this variable).

By default, if an inst.init script is located in a distribution directory, users are notified of the pending execution of the script whenever they specify the distribution directory during an installation session. Unless the user specifies otherwise, inst.init executes after the notification. If the specified distribution directory is a remote directory, inst.init is copied to the target system to execute (any scripts that inst.init calls are not copied to the target system, however).

For example, assume that a user on babyface enters one of these commands to install from server easyboy:

# inst -f easyboy:/d1/IRIX_6.2/dist
Inst> from easyboy:/d1/IRIX_6.2/dist

If easyboy 's /d1/.IRIX_6.2/dist contains a copy of inst.init, either of the previous commands copies and executes inst.init on babyface before the Inst Main menu is displayed. Similarly, inst.init is executed if it is located in the distribution directory when a Software Manager user uses the Lookup button.

Syntax of the inst.init Script
Writing an inst.init Script