Ignite-UX Custom Configuration files

For the physi
cal volume statement, you need only supply the name of the disk used as the root disk.
(The disk[] keyword takes a hardware path or index number, and returns the name of the disk.)
This discussion assumes you are defining the boot disk as a whole disk
46
.
_hp_disk_layout == "Whole disk with VxFS" |
_hp_disk_layout == "Whole disk (not LVM) with HFS"
{
partitioned_disk
{
The file system partition on a partitioned disk must be HFS for HP9000 systems. It follows from the
fact that the PA-RISC boot loader can only read from some types of HFS file systems (large files-
enabled HFS file systems cannot be booted from on PA-RISC systems). Therefore, the usage
statement is set to HFS. You set the block size and the fragment size
47
to the HFS defaults defined
earlier.
Size is set to “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). The size of the file system is all the remaining space on the disk (after swap has
been allocated).
When the disk layouts were defined earlier, “Whole disk with VxFS” was only available for HP
Integrity servers.
physical_volume disk[_hp_root_disk]
fs_partition {
_hp_disk_layout == "Whole disk with VxFS"
{
usage = VxFS
blksize = _hp_VxFS_blksize
} else {
usage = HFS
blksize = _hp_HFS_blksize
fragsize = _hp_HFS_fragsize
}
size = remaining
mount_point = "/"
}
Now you have your primary 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 the space it can (up to _hp_pri_swap), but does not go lower than
_hp_min_swap, while ensuring the file system partition gets enough to meet its impacts
48
statements requirements.
46
You can have multiple whole disks defined in a configuration. Each whole disk is defined by different
partitioned_disk definitions and has a different mount_point.
47
These concepts are only meaningful in a HFS file system. The block size is the largest block of data a file can have
allocated to it (files that can occupy a full free block will do so and the smallest amount of space that can be allocated by a
file is the fragment size. In extent-based file systems these concepts are usually meaningless. For example, the smallest
allocation unit is 1KB no matter what the fragment size is set to for the file system.
48
Impact statements and software are discussed later.
74