HP 9000 Manual page 157

Config files which describe software available from SD depots can be
automatically generated via an Ignite-UX tool called
make_config(1m). This tool produces one config file per SD depot.
Software description config files are located in
/var/opt/ignite/data/Rel_release/*.
• Software description of an archive.
Config files can be hand built to allow access to non-SD archives
(templates are provided with the Ignite-UX product in
/opt/ignite/data/examples/ to give you a good starting point).
Archives may be in either tar or cpio format. Archive software
description config files are also located in
/var/opt/ignite/data/Rel_release/*.
• Local configuration overrides that apply globally.
It is often convenient to specify defaults which will be applied to every
machine in- stalled from a particular server. For example, you might
want to specify the same NIS domain for all machines. Such overrides
should be placed in the /var/opt/ignite/config.local file.
• Boot control parameters and networking information
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
Appendix B
Using Configuration Files
Introduction
157