Ignite-UX Reference (March 2010, B3921-90005)

instl_adm(4) instl_adm(4)
NAME
instl_adm − Ignite-UX configuration file syntax
DESCRIPTION
The Ignite-UX configuration files determine the default system configurations available during the process
of installing the HP-UX operating system.
The Ignite-UX process uses configuration files to bring in default parameters, as well as, determine how the
system will be configured. During the installation process, you are presented with a user interface (UI) that
allows you to make selections that are implemented inside the configuration files as variables, use models,
and software selections. The UI also allows the user to make modifications beyond what is specified by
these constructs (such as adding new file systems or volumes).
Once you approve the configuration, a configuration file is created. This file contains only the changes
made in UI. This configuration file is then passed on to another utility that actually performs the system
configuration and software installation.
Organization and Indexing of Configuration Files
Although all configuration files use the same basic syntax, the information supplied by them is split into
multiple files to allow them to be maintained individually. These configuration files fall into the basic
classes of:
• Default disk and file system layout. Located in
/opt/ignite/data/Rel_release/config
• Software description of a single Software Distributor (SD) depot,
or system archive. Located in /var/opt/ignite/data/Rel_release/file
• Local configuration overrides that apply globally. Located in
/var/opt/ignite/data/config.local
• Named configurations created by saving a configuration via the UI.
Located in /var/opt/ignite/data/saved_cfgs/*
• Client-specific configuration files. Located in
/var/opt/ignite/clients/0xLLA/config
• Boot control parameters and networking information. Located in the
first 8KB of the file /opt/ignite/boot/Rel_release/*INSTALLFS managed by the
instl_adm utility.
To completely describe all aspects of a system, it is necessary for Ignite-UX to read multiple configuration
files as a combined set.
The grouping of configuration files into a set (known as a "configuration clause" or just "cfg clause") is
accomplished with the use of the INDEX files: /var/opt/ignite/data/INDEX or
/var/opt/ignite/clients/0xLLA/CINDEX
The INDEX file may contain multiple configuration clauses (groups of configuration files) that together
describe a unique system configuration. The UI allows the user to choose from the configurations clauses
that are defined in the INDEX file.
Similarly, the CINDEX file can contain configuration clauses, but these are only available for use by the
specific client corresponding to the per-client directory it exists in. The CINDEX file is typically used by
the make_net_recovery command to reference configuration files created for each recovery backup
performed for that client. The paths to configuration files in the CINDEX file can be relative paths, in
which case they will be accessed from within the per-client directory. The configuration clauses listed in
both the INDEX and CINDEX files are available for use during an installation or recovery of the specific
client.
The default INDEX configuration clauses provided with Ignite-UX are used to define the aspects of each
HP-UX release that Ignite-UX supports. A separate configuration clause per HP-UX release is necessary
because each HP-UX release has different defaults for file system layout and software bundling.
1