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

make_config(1M) make_config(1M)
−x option
Specify particular optional behaviors.
The options available via -x are:
allow_missing_content
By default, an error is given if any bundles that an B.11.31 or later operating envi-
ronment calls out as "required" are missing from the depot. If -x
allow_missing_content is provided, then only a warning message will be
given in this case and the config file will be produced excluding any missing bun-
dles.
no_sd_server
This option instructs make_config to generate sw_source statements in the
configuration files which do not reference a particular SD server or depot. This is
useful for generating configuration files which will end up on install media. The
assumption is that the depot is found at / on the CD/DVD media. If the depot is
not located at /, that will require additional work by specifying the
sd_depot_dir attribute yourself.
sd_host_name=hostname|ip
sw_source.sd_server entries in the configuration file will have a different IP
address for the server than the default. This is useful if your server has multiple IP
addresses and you wish to use one other than the default.
load_order=number
This option allows you to specify a relative load order in the sw_source state-
ment in the configuration file. It is only valid when used with the -c option. If the
depot contains HPUXEnvironment, HPUXBaseOS, OpEnvironments or Lan-
guagesUI bundles, the load order is automatically 0 (or 1 in certain circumstances)
and this option is ignored. If the depot contains extension software, the load order
is automatically six (6) and this option is ignored. For all other depots, this option
may be used to change the default load order of five (5) to a desired load order
greater than zero (0).
no_full_sd_spec
This option specifies that the sw_sel.sd_software_list entries in the con-
figuration file will reference bundles by their SD tags instead of by their full soft-
ware specification. This is useful when the underlying depot will be undergoing
frequent changes to the SD revision attributes and you do not wish to run
make_config each time the depot has changed. Note that this option is danger-
ous since there are no guarantees that the resulting configuration file will closely
match the depot over time.
-? Displays the help screen.
International Code Set Support
Ignite-UX uses a variety of system commands to accomplish its functionality. Because the output of many
of these commands is parsed, Ignite-UX ensures that the POSIX locale is normally used by modifying envi-
ronment variables. Help text and some command output not parsed by Ignite-UX will be left in the user’s
specified locale.
EXAMPLES
Process all of the depots found in /var/opt/ignite/depots/Rel_B.11.23 and create configura-
tion files for them in /var/opt/ignite/data/Rel_B.11.23. Make sure all of the created configu-
ration files are in each of the B.11.23 cfg clauses in /var/opt/ignite/data/INDEX:
make_config -r B.11.23
Process a single depot (/var/opt/ignite/depots/Rel_B.11.23/depot1) found in
/var/opt/ignite/depots/Rel_B.11.23 and create the configuration file for it in
3