Ignite-UX Custom Configuration files

-c /var/opt/ignite/data/Rel_B.11.11/core_cfg
Warning:
HP does not support placing different versions of an OE in one depot.
Instead, you
must keep different OEs in different depots.
This creates the configuration file that describes the depot in
/var/opt/ignite/data/Rel_B.11.11 and it is named core_cfg
81
. However, it does not
update /var/opt/ignite/INDEX so that you can create your own custom cfg clause later. If
everything completes successfully, you should see the following message only:
NOTE: make_config can sometimes take a long time to complete. Please be
patient!
An alternative to this is to use the following command:
make_config –r B.11.11
This command automatically creates configuration files for all of the depots under
/var/opt/ignite/depots/Rel_B.11.11. However, this form of the command will also
update the /var/opt/ignite/INDEX file (typically updating all cfg clauses affecting the given
HP-UX release with information about the configuration files). This may not be desirable.
For example, if you run the following command:
make_config -r B.11.11 -s core_1203_mc
Then the configuration file will be created and the /var/opt/ignite/INDEX file will be updated
(only showing the Default B.11.11 clause) to be:
# cat /var/opt/ignite/INDEX
...
cfg "HP-UX B.11.11 Default" {
description "This selection supplies the default system configuration
that HP supplies for the B.11.11 release."
"/opt/ignite/data/Rel_B.11.11/config"
"/opt/ignite/data/Rel_B.11.11/hw_patches_cfg"
"/var/opt/ignite/data/Rel_B.11.11/core_1203_mc_cfg"
"/var/opt/ignite/config.local"
}
If you then run the following command:
make_config -r B.11.11
81
This is why it was suggested earlier that if you have multiple core operating system (OE) depots, you should give them names that include
the release date of the media and an indication (if required) of the OE type.
174