make_config.1m (2012 03)

m
make_config(1M) make_config(1M)
-a 700|800|both
Specify the architecture of the bundles which should be processed (matches the
bundle.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 pro-
cess 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 statements.
For example, if level is 1, impacts statements might be generated for /usr and
/var.If
level 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 performance reasons. The
default is 1.
-i Process bundles in the specified depot(s) which are factory-ignitable (those with the
factory_integrate
attribute, bundle.hp_ii.factory_integrate, set to TRUE).
By default, all bundles are processed.
When this option is specified, the
hp_ii corequisite and load_with attributes will be
respected. This means other bundles listed as corequisites will automatically be loaded when
the bundle with the corequisite is loaded. Likewise, when a bundle which matches the
load_with attribute is selected, the bundle with the load_with will also be selected.
-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 saving 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.
-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 environ-
ment 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 bundles.
2 Hewlett-Packard Company − 2 − HP-UX 11i Version 3: March 2012