
In conjunction with the earlier form of manage_index used to list out the names of cfg clauses in an INDEX file, the preceding command can be used to ensure that all of the configuration files referenced in an INDEX file are present and, as far as can be determined, correct.
Display the description of a cfg clauseThis last form of manage_index is used to display the description of the cfg clause:
manage_index
For example:
$ manage_index
Using the make_bundles command
Why do you need to use make_bundles?The make_bundles command is necessary when usingmake_config only work with software that is contained within a bundle. Therefore, if you create a configuration file for a depot and it contains software that is packaged only as an SD product, it is not listed in a configuration file created by make_config.
Choosing which form of make_bundles to useThe make_bundles command has the following three forms:/opt/ignite/bin/make_bundles
/opt/ignite/bin/make_bundles
/opt/ignite/bin/make_bundles
The make_bundles command is primarily controlled by the
7In some forms of make_bundles, the use of
8You cannot have a standalone fileset because it must be contained within a product.
9If you perform a swlist operation on a depot, the default output shows all bundles in the depot followed by all products not contained within a bundle.
25