Ignite-UX Custom Configuration files

Configuration examples
The following section presents several different disk configuration examples. They may prove useful
when developing your own configurations.
This section does not discuss the extra space that may be allocated to file systems because of
impacts configuration statements or the effect that variables such as _hp_addnl_pct_free or
_hp_efi_partition_size may have.
Example One (custom disk layout)
This example defines a configuration that is dependent on whether or not a particular software
product is installed:
#
# This config file builds on top of the default config file for
# an OS release since it reuses some of the same variables.
# It should be included into a cfg clause in the index file after
# the default config file for a release. The following software
# should be defined in any clauses that includes this file:
# "Product XYZ"
# "Product XYZ - 4GL"
#
Remember that if you change the disk configuration, the disk layout name is changed to "Modified
LVM Layout". Consequently, things defined in the configuration may no longer be evaluated
anymore. For example, you can set the name of the volume group in the configuration in this
example using the Additional button on the Basic tab in the Ignite-UX GUI (see
_my_volume_name later in this section). However, once you modify some part of the disk layout,
the name of the layout becomes "Modified LVM Layout" and changing the value of
_my_volume_name no longer has any effect.
The name is defined by using the selection list produced by the Additional button on the Basic
tab in the Ignite-UX GUI. For the selection, "Name of the root volume group" you can select vg00
or vgroot. However, you can also enter a new name into the field and that will be used (since it
was not defined as an enum you cannot enforce a choice from the available names).
The name can be changed on the Additional button. However, it only takes effect when the disk
layout selected is "Custom configuration for Product XYZ".
#
# Allow the user to change the name of the root volume group
#
_my_volume_name = { "vg00" , "vgroot" }
init _my_volume_name = "vg00"
_my_volume_name help_text "Name of root volume group"
_my_volume_name visible_if TRUE
Here a new disk layout name is being added to the configuration without setting it as one of the
choices. This configuration file builds on top of the existing default operating system release
configuration file. It is not a replacement because many variables need to be defined that are not
worth the effort to set.
131