init _hp_service_partition_size = 400Mb

_hp_service_partition_size help_text "HP Service Partition (KB)" } else {

_hp_efi_partition_size visible_if false

_hp_service_partition_size visible_if false

}

The following shows the start of a definition for the _hp_disk_layout variable, which is set to one of several possible values depending on if this is a HP9000 or HP Integrity system.

Around the _hp_disk_layout is a test for is_ia64 and is_hppa (is HP Integrity or PA- RISC/HP9000 system). Disk layouts specific to those different types of systems are defined. The reason for converting some of the string for backwards compatibility is that older custom configuration files may refer to the names previously used for a disk layout. This would break those older configuration files, so the new names that appear in itool for the disk layouts are mapped to the older names for compatibility with older configuration files.

You actually get to see the value of the variable _hp_disk_layout when you use the Ignite-UX GUI. The values currently assigned to _hp_disk_layout are shown on the File System: list on the Basic tab. The form used in the next example to initialize a list of possible values allows the Ignite-UX GUI to modify the list later.

Further in the configuration file, when giving _hp_disk_layout a final value, you only assign its value using init. When using the form "init _hp_disk_layout="…", the Ignite-UX GUI is still allowed to modify the value. If you instead define "_hp_disk_layout="…"" without the init, the Ignite-UX GUI cannot change this value. If the Ignite-UX GUI were not able to change the value of _hp_disk_layout, no changes made in the Ignite-UX GUI to file system attributes are applied to the system41.

This is because the Ignite-UX GUI must change the value of _hp_disk_layout to "Modified LVM Layout", "Modified VxVM Layout", or "Modified Whole-Disk Layout" when changes have been made on the File System tab in the Ignite-UX GUI. If the Ignite-UX GUI is not allowed to change the variable, you cannot keep any file system customizations. This concept becomes very important when creating custom configuration files.

#######################################################################

#Any _hp_disk_layout variable setting besides those below will disable

#the default disk layout described in this file. This can be

#done if a custom disk layout is defined elsewhere.

#

is_ia64 { _hp_disk_layout = {

"VERITAS Volume Manager (VxVM) with VxFS", "Whole disk with VxFS",

"Logical Volume Manager (LVM) with VxFS"

}

}

#For PA architecture only is_hppa {

_hp_disk_layout = {

"Whole disk (not LVM) with HFS",

41The itool command Ignite-UX GUI accepts changes to file system attributes and does not caution you, but no file system attribute changes made in the Ignite-UX GUI are applied to the system.

68