User's Guide

Additional d

ialog box, use models look visibly different from variables. Later in the configuration

file is the impact statement this use model would have when it is set to true.

INIT "Create /export volume" = false

Now you have another effects relationship, this time between a new variable

_hp_root_grp_disks and _hp_root_disk. The variable _hp_root_grp_disks is meant

to be an integer, so when doing the effects relationship you add zero (0) to

disk[_hp_root_disk].size to ensure that the final value is an integer. Since variables are

not explicitly typed, you want to imply an integer type.

The variable _hp_root_grp_disks is also an enum; it can take one of the values from 1 up to

the value of variable num_disks,

and it has a default initial value of 1.

That is followed by the usage model "Create separate volumes (/usr, /var, ...)". This is used to

decide if there will be only one large root file system or if separate file systems will be created (it

would be unusual to set this to FALSE).

# Number of disks in the root volume group

# The fist line below is just to define an "effects" relationship

# between the root disk and _hp_root_grp_disks which dependent

# upon each other in the logic to follow.

init _hp_root_grp_disks = (disk[_hp_root_disk].size+0) # +0 convert to int

enum _hp_root_grp_disks

_hp_root_grp_disks = { 1..num_disks }

init _hp_root_grp_disks = 1

_hp_root_grp_disks help_text "# of disks in root VG"

INIT "Create separate volumes (/usr, /var, ...)" = TRUE

The first disk configuration "Whole disk (not LVM) with HFS" is protected by a test of the variable

_hp_disk_config to see if it is equal to "Whole disk (not LVM) with HFS".

After that, the partitioned_disk keyword starts the definition of a whole disk layout for a

system. The partitioned_disk disk definition must contain the following:

 A physical_volume definition

 An fs_partition definition

 A swap_partition definition

If you have no fs_partition definition that at least defines the root file system, the following

error appears after pressing Go! in the Ignite-UX GUI:

ERROR: There is no root volume (mount point = /) defined in the configuration.

If you have no swap_partition defined, you see the following error after selecting Go! in the

Ignite-UX GUI:

ERROR: There is no swap volume defined in the root volume group (or on the

root disk).

A built-in variable that is a count of the number of disks discovered on the system. Refer, refer to instl_adm(4).