make_config.1m (2012 03)

ManualsBrandsHP ManualsSoftwareHP-UX Manpages

make_conﬁg(1M) make_conﬁg(1M)

NAME

make_conﬁg - build Ignite-UX conﬁguration ﬁles for SD depots

SYNOPSIS

/opt/ignite/bin/make_config -r

release [ -o os_release ][-l level ][-i ][-p

][-s

release_relative_source_depot] [

-v ][-x option ][-d percent ][

-? ]

/opt/ignite/bin/make_config -s

source_depot -c conﬁguration_ﬁle [ -a 700|800|both

]

[

-f software_ﬁle][

-o os_release ][-l level ][-i ][-p ][-d percent ]

[

-v ][-x option ][

-? ]

DESCRIPTION

make_config constructs Ignite-UX conﬁguration ﬁles which correspond to Software Distributor (SD)

depots. When an SD depot is used as part of the Ignite-UX process, it must have a conﬁg ﬁle which

describes the contents of the depot to Ignite-UX. This command may automatically construct such a

conﬁg ﬁle given the name of an SD depot on which to operate. This command should be run when adding

or changing a depot that will be used by Ignite-UX.

make_config only generates information for SD bundles within a depot. All HP software is packaged in

SD bundle form; products not contained in bundles are ignored.

make_config uses the names of the depot(s) and conﬁguration ﬁle(s) to give it clues about what type of

conﬁguration ﬁle to produce. If the name contains a "700", the resulting conﬁguration ﬁle will only be

used on Series 700 target machines. If the name contains an "800", the resulting conﬁguration ﬁle will

only be used on Series 800 target machines. The -a 700|800|both option performs a similar func-

tion, with appropriate arguments, to specify the type of conﬁguration ﬁle.

Generally

make_config produces a sw_sel clause for each bundle it ﬁnds in the depot. The tag for

the sw_sel is the same as the bundle tag. When multiple bundles in the depot have the same tag (but

different architecture, revision, or vendor attributes),

make_config will build multiple sw_sel

clauses with tags differentiated by revision, architecture, or vendor, and make them exrequisites of each

other (see instl_adm (4)). If these bundles are "always load" bundles, this will result in an error and no

ﬁle will be produced. make_config produces a header in the ﬁle that shows the name of the ﬁle pro-

duced, its creation time, and the Ignite-UX version installed when make_config was used to create the

ﬁle. Note that later versions of Ignite-UX should always be able to parse a conﬁg ﬁle produced by an ear-

lier version.

Errors are always logged to

stderr. More detail may often be found in the log ﬁle at:

/var/opt/ignite/logs/make_config

Options

make_config recognizes the following options:

-r release

Construct conﬁguration ﬁles for each of the depots found in the default depots directory for the

speciﬁed release. Ensure that the newly constructed conﬁguration ﬁles are included in each of

the conﬁguration clauses for the speciﬁed release in the ﬁle

/var/opt/ignite/data/INDEX.

For example, if the speciﬁed release is B.11.23, a conﬁguration ﬁle will be generated for each

depot found in the

/var/opt/ignite/depots/Rel_B.11.23

directory. The generated

conﬁguration ﬁles will be placed in the

/var/opt/ignite/data/Rel_B.11.23

direc-

tory. The conﬁguration ﬁles will have the same name as their associated depots, with an

appended

_cfg. For instance, the

/var/opt/ignite/data/Rel_B.11.23/core_700_cfg

conﬁguration ﬁle will be gen-

erated from the

/var/opt/ignite/depots/Rel_B.11.23/core_700

depot.

-s release_relative_source_depot is also speciﬁed, the depot named must be relative to the

directory implied from the release speciﬁed by -r.

-s source_depot

Specify a single source depot to process. The depot is speciﬁed just as in the SD commands. 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 conﬁguration ﬁle.

HP-UX 11i Version 3: March 2012 − 1 − Hewlett-Packard Company 1

Summary of content (4 pages)

PAGE 1
make_config(1M) make_config(1M) NAME make_config - build Ignite-UX configuration files for SD depots SYNOPSIS /opt/ignite/bin/make_config -r release [ -o os_release ] [ -l level ] [ -i ] [ -p ] [ -s release_relative_source_depot] [ -v ] [ -x option ] [ -d percent ] [ -? ] /opt/ignite/bin/make_config -s source_depot -c configuration_file [ -a 700|800|both ] [ -f software_file ] [ -o os_release ] [ -l level ] [ -i ] [ -p ] [ -d percent ] [ -v ] [ -x option ] [ -? ] DESCRIPTION make_config constructs Ignit
PAGE 2
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.
PAGE 3
make_config(1M) make_config(1M) 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.
PAGE 4
make_config(1M) make_config(1M) EXAMPLES Process all of the depots found in /var/opt/ignite/depots/Rel_B.11.23 and create configuration files for them in /var/opt/ignite/data/Rel_B.11.23. Make sure all of the created configuration 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) /var/opt/ignite/depots/Rel_B.11.23 and create the configuration file /var/opt/ignite/data/Rel_B.11.