Now size is set to the remaining, which takes whatever space is left over once "other" things (in this case swap at the end of the disk) have been allocated., The mount point naturally is "/" (since it is the root file system). Lastly, if this is a very small disk change minfree to be 5% (you are installing B.11.11 and there is no way you can fit B.11.11 onto a 300MB disk anyway).

fs_partition { usage = HFS

blksize = _hp_HFS_blksize fragsize = _hp_HFS_fragsize size = remaining mount_point = "/"

disk[_hp_root_disk].size < 300Mb {

#For really small disks, tune down minfree

#in order to gain some disk space.

minfree = 5

}

}

Now you have our primary (and presumably only) swap partition definition, you can see that it is swap from the usage. The interesting thing is the size specification. This sets the size to be at least _hp_min_swap but also includes any remaining space up to _hp_pri_swap in size. The swap space in this case attempts to get all of the space that it can (up to _hp_pri_swap) but does not go lower than _hp_min_swap while ensuring that the file system partition gets enough to meet its impacts27 statements requirements.

swap_partition { usage = SWAP

mount_point = "primary"

size = _hp_min_swap remaining _hp_pri_swap

}

}

}

Now you have all the volume manager layouts. You may have noticed at the beginning of this section that LVM and VxVM both use the same ways of defining volume definitions; only the usage statement at the volume group level determines if an LVM volume group or VxVM disk group will be created (see below).

_hp_disk_layout == "VERITAS Volume Manager (VxVM) with VxFS" _hp_disk_layout == "Logical Volume Manager (LVM) with HFS" _hp_disk_layout == "Logical Volume Manager (LVM) with VxFS"

{

Here you are defining the variable _hp_group_name. However, you must first make sure that it is not visible on the Additional button (since you do not want anyone to be able to change it). If the value of _hp_disk_layout is set to be VxVM ("VERITAS Volume Manager (VxVM) with VxFS") you set _hp_group_name to be rootdg; otherwise it is LVM you are using and vg00 is the name you are going to use28.

27Impact statements and software are discussed later.

28VxVM 3.5 and earlier requires the root volume group be named rootdg. This is enforced by Ignite-UX.

52