Ignite-UX Reference (March 2010, B3921-90005)

ignite(5) ignite(5)
Enabling (or updating) an existing depot
If you already have an SD depot available, or if you have made changes to a
depot about which Ignite-UX knows, you may use the make_config and
manage_index commands to generate a configuration file that Ignite-UX
will use to access the depot. For example:
make_config -s server:/depot_1123 \
-c /var/opt/ignite/data/Rel_B.11.23/core_cfg
manage_index -a -f \
/var/opt/ignite/data/Rel_B.11.23/core_cfg
If at a later time, you modify the contents of a depot (for example, using
swcopy to add software), the same make_config step will need to be
rerun in order for Ignite-UX to be aware of the modifications.
Note: The make_config command only operates on software that is
contained in a bundle. If you have a depot that has products not in a bun-
dle, you may run the make_bundles command on the depot prior to
running make_config.
For non-SD (archive) operating system software:
Ignite-UX has the capability of loading a client from an archive image taken from a
client that represents a standard configuration. This method gives significantly faster
install times, but may not be as flexible as using an SD source.
You will first need to generate the archive image of a client in the desired state. It is
recommended that the /opt/ignite/data/scripts/make_sys_image
script be used to accomplish this task.
Once an archive image is created, a configuration file that represents the location and
attributes of that image must be created before Ignite-UX may use it.
A sample of a config file that may be used with a core archive may be found at:
/opt/ignite/data/examples/B.11.23.archives.cfg
The comments in this example file describe where to copy the file and what to
change in the file to make it reference your archive and work in your environment.
4. Add additional applications (optional).
If you have other software you would like to hav e loaded during the client installation, you
may create configuration files similar to what was done for the core operating system soft-
ware by using make_config and manage_index or by using an example configuration
file and modifying it.
For SD application software:
Run the following commands for each depot you plan to load SD software from dur-
ing the installation. The make_config command only handles SD software that
is packaged in bundle form. If the SD depot you want to use has software not con-
tained in a bundle (for example, a collection of patches), the make_bundles
command may be used to create bundles in the depot.
make_bundles /depots/11.23_patches
make_config -s server:/depots/11.23_patches \
-c /var/opt/ignite/data/Rel_B.11.23/patches_cfg
manage_index -a -f /var/opt/ignite/data/Rel_B.11.23/patches_cfg
To make a depot containing compilers available which are already in bundles (no
need to use make_bundles):
3