}

init sw_sel "Run site commands" {

description = "Run site commands after OS loaded" sw_source = "site commands"

sw_category = "SiteSpecific"

post_load_script="/var/opt/ignite/scripts/run_after_load" } = TRUE

The difference between this method and placing a post_load_cmd into the core operating system load sw_sel is that you have the opportunity to prevent the commands from running the Ignite-UX GUI by deselecting the software (even though in this case there really is no "software").

However, be aware that any script you run must be either accessible using tftp, if this is a network installation, or located in the SCRIPTS file, if the installation is happening from media (in the LIF produced by make_medialif ).

If you want to run a script that has already been installed with other software, use a cmd hook instead of a script hook:

init sw_sel "Run site commands" {

description = "Run site commands after OS loaded" sw_source = "site commands"

sw_category = "SiteSpecific"

post_load_cmd="/opt/site/bin/run_after_load" } = TRUE

You must ensure that the load order associated with the sw_source prevents the "cmd"

sw_source from running until after any software that it depends on has been loaded (if it has dependencies).

Using a sw_sel to apply kernel parameters

You can use a sw_sel clause to control the application of kernel parameters to a system, as well. The Ignite-UX configuration items that can be used to change kernel parameters (from the instl_adm(4) manpage) are as follows:

mod_kernel = cplx-string mod_kernel += cplx-string

This keyword can be used to add drivers or tunable parameters to the system's kernel that is built during the Ignite-UX process. The format of cplx-string may be either "driver" or "tunable value".

The largest of any tunable parameter that exists in either the /stand/system file or that is specified will be used. Beginning with the 11.23 release, if a tunable is not found in /stand/system, then it will also be compared with the default value as reported by kctune. Ignite-UX does not compare the values of formulas to discrete numerical values, or two formulas, or hexadecimal values, in order to determine which is larger. It will issue a note message stating that it will assume the last mod_kernel keyword parsed is larger (regardless of whether it is a formula or discrete numerical value) and will apply it. There is no bounds checking done on tunable parameters.

Decimal values should be in the range from 0 to 2147483647 (2"31-1). The shell that is used to evaluate these values uses

123