Installing HP-UX 11.0 and Updating HP-UX 10.x to 11.0 HP 9000 Computers Edition 1

Appendix B 223
Using Configuration Files
Types of Config Files
It is possible to specify defaults for attributes like the IP address of
the Ignite-UX server and whether to run a UI to install a new target.
These can be specified in the first 8 KB of the install file system
(/opt/ignite/boot/INSTALLFS). This information is added or
deleted with the instl_adm(1m) command.
• Client-specific configuration files.
Each client which is to be installed has a configuration file which is
peculiar to it located at
/var/opt/ignite/clients/0xLLA/config, where LLA is the
link-level address of the client. This file is typically created as a result
of running the user interface to specify the target machine
configuration.
This file usually refers to other config files mentioned above. It also
contains specific directives to override what may have been defined in
the other files. For example, you may wish to customize the disk
layout beyond what the defaults in
/opt/ignite/data/Rel_release/config allow. The customizations
end up in /var/opt/ignite/clients/0xLLA/config.
• Named configurations created by saving a configuration via the UI
You can create your own default configurations via the UI and save
them for future use. For example, you might have a large number of
users with similar machines who all run CAD tools. You could build a
configuration which matches what they need and save it in a
configuration called "CAD System". When you need to install a new
system of this type, you can select "CAD System" from the UI and
you're done (or you could customize it further using "CAD System" as
a starting point). Saved configurations are located in
/var/opt/ignite/saved_cfgs/*.
Other Customized Building Blocks
You can also build your own config files to specify a particular building
block you are interested in, and then combine them in arbitrary ways.
These building block config files should be located in
/var/opt/ignite/data/Rel_{release}/*.