Ignite-UX Custom Configuration files

Defining a custom software configuration
The section of instl_adm(4) that defines software configuration is quite long but very useful -
only sections of it are discussed here. If you require more information, review the section titled
"Software Source and Selections".
Do not attempt to write configuration files for SD depots. Instead use the make_config command
because it correctly defines all configuration data needed. You can then customize the
configuration file produced by make_config.
The general structure for specifying software is as follows:
sw_source src-tag-string
{
source-attributes...
}
sw_category cat-tag-string
{
description = string
}
sw_sel sel-tag-string
{
sw_source src-tag-string
sw_category cat-tag-string
selection-attributes...
}
init sw_sel
sel-tag-string=Boolean
Looking at a network recovery sw_source and sw_sel
To see how software is defined, look at the way that make_net_recovery builds a definition of
an archive:
sw_source "core archive"{
description = "Recovery Archive"
load_order = 0
source_format = archive
change_media = FALSE
post_load_script = "/opt/ignite/data/scripts/os_arch_post_l"
post_config_script = "/opt/ignite/data/scripts/os_arch_post_c"
# if nfs_source is used, be sure to export the source.
(source_type == "NET") {
nfs_source = "10.0.0.1:/var/opt/ignite/recovery/archives/systema"
}
# ftp_source and remsh_source are alternate ways to copy
# the archive. An example of the ftp syntax:
# ftp_source = "anonymous@15.1.54.123:iux"
# remsh_source = "user@15.1.54.123"
}
In the above example, there is a sw_source definition called core archive that has a
description of Recovery Archive. The archive is loaded at load order 0 (this is a requirement
120