HP 9000 Manual page 69

2. For non-SD OS software:
Add additional If you have other software that you would like to pull during your install
applications (optional)
and want to have the software made available for selection in the
Ignite-UX UI, run the make_config and manage_index tools on those
depots. If the contents are not 700/800 specific, then the -a[78]00
option should not be used.
For SD application 1. Run the following commands for each depot you plan to load SD
software
Chapter 4
To use a depot other than /dev/dsk/c0t2d0 to read the software,
you can specify the depot with the -s option.
For example, the following would apply if you already have an OS
depot, or you have made modifications to it. Then you can use the
make_config and manage_index commands to generate a
configuration file. For example:
# make_config -s server:/depot_700 \
-c /var/opt/ignite/data/Rel_B.10.20/core_700
# manage_index -a -f /var/opt/ignite/data/Rel_B.10.20/core_700
See the ignite(5) man page for further examples.
If the source is not an SD depot (i.e., it is an archive image), then the
add_release command is not applicable.
You will need to create a unique config file that represents the non-SD
operating system software. A sample of a config file that does a core
archive can be found at the following location:
/opt/ignite/data/examples/core.cfg
After copying this file and making edits to it as instructed in the
comments contained in the file, you can use the manage_index tool
to insert a reference to this configuration in the following location:
/var/opt/ignite/INDEX
software from during the installation. The make_config tool only
handles SD software which is packaged in bundle form. (All
HP-supplied software is packaged in this form. See the
make_bundles(1M) manpage for information on making SD bundles
in an SD depot.)
For example, to make compiler depot bundles available type the
following:
Configuring an Ignite-UX Server
Setting Up an Ignite-UX Server
69