Ignite-UX Custom Configuration files

The cfg clause needs the following information:
1. A name (for example, HP-UX B.11.11 Default)
2. A description (see the description keyword)
3. A list of one or more configuration files referenced by this cfg clause
4. One or more configuration files that define software that may be installed
4
When a cfg clause is selected (it has been set to TRUE and nothing of higher precedence
changes this), its configuration files are processed in order and evaluated. This turns the set of
configuration files into something that a client can use to install itself.
The make_net_recovery configuration files
A make_net_recovery session always creates the same configuration files, and you can see
what they are by looking at a cfg clause in a CINDEX file:
cfg "2003-10-08,12:45 Recovery Archive" {
description "Recovery Archive"
"recovery/2003-10-08,12:45/system_cfg"
"recovery/2003-10-08,12:45/control_cfg"
"recovery/2003-10-08,12:45/archive_cfg"
}
The three configuration files are as follows:
1. system_cfg –-
This file is produced by the save_config command. It contains the file system layout,
networking information, and hardware instance numbers for the system.
2. control_cfg
This file contains definitions of Ignite-UX variables and the commands needed to import volume
groups back into the final system.
3. archive_cfg
This file contains the software definition of the archive that is used for recovery (including impacts
keywords, etc.).
The CINDEX file provides a higher level of precedence than the INDEX file, so any cfg clause
selected in the CINDEX file is used in preference to anything in the INDEX file in a non-interactive
installation for a system. In an interactive installation, the recovery archive is automatically selected
for installation so you can manually select another configuration for installation on the Basic tab in
the Ignite-UX GUI.
The make_tape_recovery configuration files
The make_tape_recovery command still creates the same three configuration files that
make_net_recovery does. For example:
# pwd
4
This cfg clause is a default clause set up by Ignite-UX. This clause, as shown, does not have any configuration files that
define software to be installed. Therefore, it is incomplete and cannot be used to install a system.
14