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

session for use in subsequent sessions. For more information regarding configuration files, see
“Using Configuration Files” (page 158).
To specify a saved configuration as the default, define it in your server’s /var/opt/ignite/
data/INDEX file, or use the bootsys command with the -i option and name you have given
it.
Specifying Defaults in the config.local File
The /var/opt/ignite/config.local file is normally included in every configuration (cfg)
clause in the /var/opt/ignite/data/INDEX file. It provides a convenient location, in which
to store default parameters that are the same for all configurations. Typically these are networking
parameters, default software selections and kernel modifications.
The following is an example of what a config.local file could look like. The sw_sel definitions
depend on what you have defined in other configuration files on the Ignite-UX server.
dns_domain="corp.com"
dns_nameserver[0] = "10.2.72.2"
nis_domain="corpdomain"
wait_for_nis_server=FALSE
root_password="JPDw02THwAhiQ"
timezone="MST7MDT"
ntpdate_server="10.1.48.1"
init sw_sel "Misc_Patches"=TRUE
init sw_sel "B3919DA_AGP"=TRUE
mod_kernel += "maxuprc 100"
set_kernel += "dbc_max_pct 20"
NOTE: After making manual edits to config.local, always use the following command to
verify that the syntax is correct and to avoid installation errors:
instl_adm -T -f config.local
Setting Defaults with instl_adm
Some network parameters must be known by the client when it first boots. The netmask and gateway
can be supplied in the installation or RAM file system ([W|V|I]INSTALLFS). You can do this by
using the instl_adm command, which has options to set the client’s netmask, gateway, Ignite-UX
/tftp server, and so on.
For example, you might want to set the keyboard language so you are never prompted for it when
booting from Ignite-UX. To do this, first display the current configuration information and redirect
it to a temporary file for editing. Then, edit the file to include the new configuration information.
Finally, apply the new configuration information from the temporary file.
In the following example, the keyboard language is set to PS2_DIN_US_English.
# instl_adm -d > /tmp/installfs.out
# echo '_hp_keyboard="PS2_DIN_US_English"' >> /tmp/installfs.out
# instl_adm -f /tmp/installfs.out
For more information, see “Using Configuration Files” (page 158) , instl_adm(1M), and instl_adm(4).
Using the Per-Client Configuration File
When Ignite-UX begins an installation session, it scans the directory /var/opt/ignite/clients
for a directory matching the MAC address of the client. For example, if the MAC address of the
client is 0x08000992E346, Ignite-UX looks for a file named config in /var/opt/ignite/
clients/0x08000992E346. However, to enable you to find clients easily Ignite-UX also creates
a symbolic link between the client’s name and the MAC address. If the client has more than one
LAN interface, the MAC address of each interface is used until a matching directory is found.
172 Automating Installations