Ignite-UX Custom Configuration files

{ _hp_min_swap = 512Mb }

(_hp_min_swap > 192Mb & disk[_hp_root_disk].size < 1800Mb)

{ _hp_min_swap = 192Mb }

(_hp_min_swap > 96Mb & disk[_hp_root_disk].size < 700Mb)

{ _hp_min_swap = 96Mb }

(_hp_min_swap > 68Mb & disk[_hp_root_disk].size < 600Mb)

{ _hp_min_swap = 68Mb }

Now _hp_sec_swap has been initialized with a set of values that can be chosen from; however,

they are not a fixed set of values. The variable _hp_sec_swap can be set using the Additional

button because of the way the variable was defined (<variable>={ value1, value2, … }).

The variable _hp_sec_swap has its value set from a selection list or by typing it into the

corresponding field directly. This can happen because _hp_sec_swap was not defined as an

"enum"; if it had been defined as an enum only a value from the list of values it contains could be

used.

Although, in this configuration, hp_pri_swap cannot be modified using the Additional button.

This value appears directly in the Ignite-UX GUI on the Basic tab using the Root Swap (MB)

button and it allows you to select from a list of possible values. The list of values shown in the

selection list for _hp_pri_swap comes from the list defined in the configuration. If you create a

custom disk configuration file, you should supply a value or a list of values for _hp_pri_swap (or

somehow otherwise calculate a default value for it).

_hp_pri_swap = { 128Mb, 256Mb, 512Mb, 1024Mb,

1536Mb, 2048Mb, 3072Mb, 4096Mb,

8192Mb, 12288Mb, 16384Mb }

_hp_sec_swap ={ 0Mb, 128Mb, 256Mb, 512Mb, 1024Mb,

1536Mb, 2048Mb, 3072Mb, 4096Mb,

8192Mb, 12288Mb, 16384Mb }

init _hp_sec_swap = 0Mb

_hp_sec_swap help_text "Secondary Swap space (KB)"

The next example gives _hp_disk_layout a value of disk [_hp_root_disk].model. If the

value of that expression ever changes, it causes the value of _hp_disk_layout to be re-

evaluated.

Doing this makes good sense in the context of this configuration file because if you change the root

disk, you may need to re-evaluate what the disk configuration is. Tests later on may override some

defaults for _hp_disk_layout in the following example:

Note:

The models being tested on are not likely ever to run HP-UX B.11.11.

This is old data b

eing carried along into later releases.

# This next statement is used only to establish an effects relationship

# between the _hp_disk_layout variable and _hp_root_disk. The value is

# overwritten below.

init _hp_disk_layout = disk[_hp_root_disk].model

The following section defines some limitations on non-LVM configuations due to firmware limitations

in older HP9000 systems - it is somewhat unlikely any of these systems are running HP-UX 11.11

(some of them supported HP-UX revisions as early as 7.x).