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

222 Appendix B
Using Configuration Files
Types of Config Files
Types of Config Files
For maintenance convenience, the configuration information is split into
several different config files. These config files fall into the following
basic classes:
• Default disk and file system layout.
Because the capabilities of each operating system release differ
somewhat, HP supplies a different set of defaults for each release.
These are located in /opt/ignite/data/ Rel_release/config,
where release is the result of the uname -r command. For example,
/opt/ignite/data/Rel_B.10.20/config contains the default
disk layouts for the HP-UX 10.20 release.
• Software description of a single SD depot.
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