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

make_config(1M) make_config(1M)
−s source_depot
Specify a single source depot to process. The depot is specified just as in the SD com-
mands. If the depot is on the local machine, specify the depot’s path name. If the depot
is on a remote machine, specify remote_host_name:remote_depot_path.
−c configuration_file
Specify the name of the resulting configuration file.
−a 700|800|both
Specify the architecture of the bundles which should be processed (matches the bun-
dle.architecture attribute). By default, all bundles are processed. If the
depot/configuration file name contains 700 or 800, only the respective configuration file
types are processed. For example, if you specify "-a 700", only bundles which are
marked as 700 or 700/800 will be processed.
This option also forces the resulting configuration file to be used only on target machines
of the appropriate architecture. The both argument may be used to force
make_config to process all bundles, even if the depot name or configuration file name
contains a "700" or "800".
−f software_file
Specifies that only the SD software selections specified in the software_file will be used
when generating the configuration file. By default, all software bundles in a depot are
processed.
−o os_release
Specify the OS release of the bundles you wish to process. Each bundle supplied by HP
has an sd(4) attribute entitled os_release that describes which OSs on which the bundle
may be installed. The sd(4) os_release attribute matches what is returned from uname
-r. By default, all bundles within a depot are processed. By specifying an os_release
value with −o, it is possible to select only those bundles in a depot that may be installed
on a particular OS.
−l level
Determines what level in the file system hierarchy for which to build impacts state-
ments. For example, if level is 1, impacts statements might be generated for /usr
and /var. If lev el is 2, impacts statements could be generated for /usr/local,
/usr/bin, and so forth. It is not recommended to specify a level greater than 2 for per-
formance reasons. The default is 1.
−d percent
Decreases the disk space impacts by this percentage for bundles that make_config
identifies as patch bundles. Since patch bundles typically replace files already installed on
a client with just an incremental increase in size, disk space impacts for these bundles can
be overstated. The allowable range for percent is 1 to 75. Caution is urged when using
this option as it may lead to file system overflow and cause the installation to fail during
the swinstall phase. If this problem happens, the configuration file(s) should be
recreated with a smaller percent value and the installation repeated. Note that
make_config will add an impact to /var equal to the sum of all the disk space
impacts before this reduction is taken which accounts for swinstall potentially sav-
ing old copies of patched files under /var/adm/sw/save.
−p Preview. This instructs make_config not to make any changes, but to write messages
to stdout explaining what would be done if preview were not enabled. Note that no
depots are read in preview mode. The only actions are to display which depot(s) will be
processed and which configuration file(s) will be generated.
−v Verbose mode. Write more detail about what was processed to the log file.
2