Ignite-UX Custom Configuration files

archive_type = gzip tar
# For NFS, the path to the archive is relative to the mount point
# specified in the sw_source:
(source_type == "NET") {
nfs_source = "10.0.0.1:/var/opt/ignite/images"
}
...
visible_if = can_run_64bit
} = TRUE
(sw_sel "golden image1") {
_hp_os_bitness = "64"
}
_hp_os_bitness visible_if false
Next, a language is set up so there is a choice of no locale English, or C locale and English. Your
choice depends on the languages that would be available depend on the system at the time the
recovery archive was created:
sw_source "no select" {
source_format = cmd
}
init sw_sel "English" {
description = "English Language Environment"
sw_source = "no select"
sw_category = "Languages"
locale = { "SET_NULL_LOCALE:English", "C:English" }
} = TRUE
Using a sw_sel to run commands instead of installing software
The following configuration acts in a similar way to the language selection earlier. The
source_format of cmd in the sw_source definitions does not cause any software to be loaded.
The load order statement forces the command to run after everything else (in case someone does
anything at the default load order of 5). The source_format of cmd gives you a great deal of
flexibility in running scripts.
You have to define any sw_category that you want to use. Before you can use a software
category, you must define a sw_category. This is not true for the sw_category
"Uncategorized"; this sw_category is applied to any software that does not explicitly define a
sw_category. If all software is given, the Uncategorized sw_category will not appear on
the Software tab in the Ignite-UX GUI. You should not explicitly assign a sw_category
Uncategorized to any software. In the following example, the sw_category of
"SiteSpecific" is defined.
The sw_sel, however, defines a post_load_cmd that runs:
sw_category "SiteSpecific" {
description = "Local Site Commands"
}
sw_source "site commands" {
source_format = cmd
load_order = 10
122