instl_adm.4 (2012 03)

i
instl_adm(4) instl_adm(4)
env_vars = cplx_string
env_vars += cplx_string
Sets a string of variables of the form variable =value that is sourced into the environment for the
duration of the installation process. The format of cplx_string should be one variable assignment
per line. The value of the assignment does not need to be quoted (unless quotes need to be part of
the value). These variable assignments are stored in the file /tmp/install.vars and is left on the
client after the installation.
The use of the
+= operator is recommended to ensure any prior settings are kept and not discarded
as is the case when the =
operator is used.
Some special environment variables that may be set inside
env_vars and are recognized by the
cold installation process are:
INST_NET_RESPONSE_TIMEOUT=
seconds
Booting an installation client from the network sets the amount of time the client waits for
you to respond before it reboots assuming the client booted from the installation server
accidentally. Setting seconds to 0 (zero) disables the timeout and the client does not prompt
for a response.
INST_ALLOW_WARNINGS=
seconds
Setting this environment variable is useful for non-interactive installation sessions when
warnings about disks containing data cause the installation to switch to interactive mode.
Setting seconds to
1 causes all warnings to be ignored and the installation to proceed. Set-
ting seconds to greater than 1 allows you that number of seconds to read the warning and
stop the installation by pressing < return >.
INST_BATCH_MODE_TIMEOUT=
seconds
Sets the amount of time you have to interrupt a non-interactive installation; the default is 10
seconds.
INST_ENABLE_NETWORK=
1
Set in the case where an automated install is to be performed from physical media and the
network interface needs to be enabled. If the host name and IP address are not set, the
install process will attempt to contact a
DHCP/bootpd server to get that information.
LOADFILE_RETRY_COUNT=
number
Used to change the default number of times the internal
loadfile command retries a
failed attempt to retrieve data from the server or media. Usually this retry mechanism is
used to overcome tftp transfer problems; the default value is 5.
Software Source and Selections
Ignite-UX supports a sophisticated mechanism for specifying the software that is available for loading
during installation. It supports loading from multiple sources of various types, primarily SD depots, and
tar/cpio/pax archives. The configuration files contain the mapping from what software selections you
see to the source that contain them. This allows you to operate on the full list of software selections
without needing to know the location of the source of the selections.
The three constructs for handling software are:
sw_source, sw_sel, and sw_category.A
sw_source specifies an SD depot, or an access method to an Ignite-UX server containing archives. The
sw_sel specifies the software contained in the SD depot, or specifies the path to an archive on the server
or media. There is typically one sw_sel definition per software bundle or archive. The
sw_category is a mechanism for grouping the multitude of sw_sels available. The UI treats some
categories specially by putting them on the basic screen or a under a special selector.
When setting up an SD depot that uses software bundles , as all software shipped by HP should, you may
simply run the
make_config command may be run against that depot to generate the configuration file
describing the software available in terms of those constructs. Setting up a configuration file that allows
access to an archive requires manual editing, and the use of the archive_impact command.
The general structure for specifying software is as follows:
sw_source src-tag-string
{
source-attributes...
}
sw_category cat-tag-string
{
HP-UX 11i Version 3: March 2012 − 25 − Hewlett-Packard Company 25