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

instl_adm(4) instl_adm(4)
Configuration files that are parsed later have precedence over any earlier files and may override values set
in earlier files. Thus, the client-specific configuration file has highest precedence.
Tape and CD media are in lif (4) format and contain an INDEX file. Typically the only file referenced by
the INDEX file is entitled CONFIG. It is this CONFIG file, in addition to the first 8KB of the
*INSTALLFS file, that make up the configuration information for these media types.
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
Setting the Default Configuration Using Logic Expressions
When configurations are saved as a named configuration, the UI creates a new INDEX file cfg clause for
that saved configuration. It may be desirable to create a logic expression to determine which saved configu-
ration is to be applied to a new client. This may be performed by setting the cfg clause to true/false
inside the *INSTALLFS file using the -f option with the instl_adm command. The *INSTALLFS
file is the proper place to retain this information. If put in an INDEX file, the UI does not preserve this
type of information the next time a save operation has completed.
# Select the "Two disk cfg" if the system has two or more disks.
cfg "Two disk cfg" = (num_disks >= 2)
# For a system with only one disk and a small amount of memory,
# select the "small system configuration".
num_disks == 1 & memory < 64MB
{
cfg "small system configuration" = true
}
Using a Software Archive
If a set of files exists that is packaged in a tar/cpio/pax archive and you want it installed during the
installation process, you should create a new configuration file similar to the following example. This cre-
ates a new software selection representing this source. It also conditionally selects this software for loading
if the root disk size is more than 1800MB.
sw_source "Per-Discipline Packs" {
description = "Software Apps for Individual Disciplines"
source_format = archive
nfs_source = "14.12.99.113:/var/opt/ignite/archives"
}
sw_category "Disciplines" {
description = "Software for Individual Disciplines"
}
sw_sel "EE pack" {
description = "Software Apps for Electrical Engineering"
sw_source = "Per-Discipline Packs"
archive_type = gzip tar
archive_path = "11.11_700_ee.gz"
sw_category = "Disciplines"
sw_category += "EE-Software"
# Use the /opt/ignite/lbin/archive_impacts tool to create the
# impacts size statements below:
impacts = "/var" 12568Kb
impacts = "/usr" 23468Kb
impacts = "/" 2Kb
37