User's Guide

# touch /var/opt/ignite/data/Rel_B.11.11/custom_cfg
# manage_index -a -f /var/opt/ignite/data/Rel_B.11.11/custom_cfg \
-c "Custom B.11.11 installation using SD"
You have a file to which you can start adding configuration information to customize the existing
configuration files. HP does not recommend that you customize configuration files generated by
Ignite-UX commands. If the software in the depot changes, it is much easier to recreate them using
Ignite-UX commands than it is to maintain them manually.
For example, rather than changing the configuration files that define a software product to set it to
be installed you can add configuration information to this new file to install the software just for this
cfg clause. This means the configuration file that describes the depot could be used in other cfg
clauses as well to define the contents of a depot without having to take additional action. You
could add the following configuration information:
init sw_sel "B3901BA"=TRUE
init sw_sel "B5725AA"=TRUE
sw_sel "ISO_patches"=TRUE
This would install the ANSI/C compiler, the complete version of Ignite-UX, and the patch bundle
you created previously onto the system being installed. Users running the Ignite-UX GUI to
interactively change the software to be installed could change whether the ANSI/C compiler or
Ignite-UX is installed. The user has no choice in the installation of the ISO patches you packaged
earlier since the software selection is set to TRUE without using init, which means that the Ignite-
UX GUI cannot change the selection.
Next, you could define a custom disk layout that is a choice between the existing disk layouts
defined in /opt/ignite/data/Rel_B.11.11/config or completely replacing them so you do
not have a choice of any of the default disk layouts. To implement this choice you would add the
following:
_hp_disk_layout = {
"MyApp custom disk layout"
}
None of the default disk layout choices defined in /opt/ignite/data/Rel_B.11.11/config
would be available (although not shown here you must define the disk layout that would be used).
Alternatively, you could use the following example that adds the new disk layout to list of available
choices and then sets it to be the default choice (anyone installing a system could still use the other
layouts defined in the /opt/ignite/data/Rel_B.11.11/config).
_hp_disk_layout += {
"MyApp custom disk layout"
}
init _hp_disk_layout="MyApp custom disk layout"
It is important to use a good foundation, building on top of the release default configuration files
and the depot (software) configuration files enables you to easily create more complex
configurations.
190