Ignite-UX Custom Configuration files

/var/opt/ignite/recovery/2004-01-12,15:23
# ll *cfg
-rw-r--r-- 1 root sys 3032 Jan 12 15:24 archive_cfg
-rw-r--r-- 1 root sys 963 Jan 12 15:24 control_cfg
-rw-r--r-- 1 root sys 7223 Jan 12 15:24 system_cfg
The main diff
erence is that the three configuration files end up in a single LIF file on the tape when
the recovery tape is created. The order of precedence here is unimportant since the tape is the
only device used and all of the configuration files are concatenated together into one LIF file
(CONFIG).
Files created by make_config
The make_config command is used to create configuration files that provide enough information
to allow the installation of software bundles from Software Distributor (SD) depots. The
make_config command is covered in a later section.
Using the manage_index command
A variety of uses
The manage_index command has many different options. This section describes every form the
command can take, as well as its uses.
You should never manually maintain INDEX files. Instead, you should always use manage_index
to maintain them. The manage_index command does not maintain any formatting or comments
that may have been added to index files by an Ignite-UX administrator.
The following are all the forms defined in manage_index(1M):
manage_index -a -f config_filename [-c cfg_clause_name| -r release]
[-p] [-v] [-i
index_filename]
manage_index -a -s script
_file_name [-p] [-v] [-i index_filename]
manage_index -d -c
cfg_clause_name | -r release [-p] [-v]
[-i
index_filename]
manage_index -e -c cfg
_clause_name [-p] [-v] [-i index_filename]
manage_index -l -c
cfg_clause_name | -r release ] [-o] [-v]
[-i index_filename]
manage_index -l -o [-v] [-i index
_filename]
manage_index -m
old_clause_name -c new_clause_name [-p] [-v]
[-i
index_filename]
manage_index -n
existing_clause_name -c new_clause_name [-p] [-v]
[-i
index_filename]
manage_index -t -f
config_file_name [-c cfg_clause_name| -r release]
[-p] [-v] [-i
index_filename]
15