Ignite-UX Custom Configuration files

usage = HFS
blksize = _hp_HFS_blksize
fragsize = _hp_HFS_fragsize
} else {
usage = VxFS
blksize = _hp_VxFS_blksize
}
size = remaining | 100Mb
_hp_root_grp_striped == "YES" {
stripes = *
stripe_size = _hp_FS_stripe_size
}
}
}
The /home volume always gets defined and has a rather small size with no minimum, going up to
20MB.
logical_volume {
mount_point = "/home"
largefiles = true
_hp_disk_layout == "Logical Volume Manager (LVM) with HFS" {
usage = HFS
blksize = _hp_HFS_blksize
fragsize = _hp_HFS_fragsize
} else {
usage = VxFS
blksize = _hp_VxFS_blksize
}
size = remaining | 20Mb
_hp_root_grp_striped == "YES" {
stripes = *
stripe_size = _hp_FS_stripe_size
}
}
} # root group
} # Volume Manager disk layout.
The following special variables are used by Ignite-UX to control aspects of the installation or
recovery. The "Special variables" section describes all of the special variables in detail.
# Set the variables that are recognized by the UI as invisible
# so that they don't show on the "Additional" screen:
_hp_locale visible_if false
_hp_cfg_detail_level visible_if false
_hp_pri_swap visible_if false
_hp_min_swap visible_if false
_hp_disk_layout visible_if false
_hp_default_cur_lan_dev visible_if false
_hp_default_final_lan_dev visible_if false
_hp_keyboard visible_if false
_hp_root_disk visible_if false
_hp_boot_dev_path visible_if false
If _hp_disk_layout is one of the volume manager values then you allow some things to become
visible in the Additional button from the Basic tab in the Ignite-UX GUI. Some of these control
some of the configuration that you have already looked at. They are only applicable if you are
using a volume manager, so the else construct makes sure that none of them can be seen on the
Additional button.
61