User's Guide

ManualsBrandsHP ManualsSoftwareHP Ignite-UX

171

172

173

174

175

176

177

178

179

180

In addition to c

reating the configuration file, the /var/opt/ignite/INDEX file will be updated

as in the following excerpt of the file:

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/data/Rel_B.11.11/core_cfg"

"/var/opt/ignite/config.local"

}

You should avoid multiple core operating system (OE) definitions within the one cfg clause. The

contents of the second configuration file defining a core operating system (OE) depot override the

configuration in the first.

This command does not cause any additional changes to occur and make_config would only

add the core_cfg configuration file to every B.11.11 clause in the INDEX file.

# make_config –r B.11.11 –s core

For information about the contents of core operating system (OE) configuration file, see the "Core

operating system depot configuration" section.

Creating a minimalist cfg clause for installation

You can create a cfg clause in /var/opt/ignite/INDEX that will allow you to install a system.

manage_index -n "HP-UX B.11.11 Default" –c \

"Custom B.11.11 installation using SD"

manage_index -a -f /var/opt/ignite/data/Rel_B.11.11/core_cfg \

-c "Custom B.11.11 installation using SD"

You use manage_index to avoid using the variations of make_config that indiscriminately

change cfg clauses in the INDEX file. In this case, you are copying the default B.11.11 clause

(the changes from make_config in the previous section have been undone prior to doing this

step).

When complete you have a new cfg clause in the INDEX file:

# cat /var/opt/ignite/INDEX

...

cfg "Custom B.11.11 installation using SD" {