User's Guide

Next is another u

se model defined called "Create separate volumes (/usr, /var, ...)". It is used

later for _hp_disk_layouts other than "Whole disk (not LVM) with HFS" only. By default, this is

TRUE (and the Ignite-UX GUI does show separate volumes for /usr, /var, … by default).

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).

For the physical volume statement, you need only supply the name of the disk that is used as the

root disk (the disk[] keyword takes a hardware path or index number and returns the name of

the disk). This discussion here assumes that you are defining the boot disk as a whole disk

However, if you were writing custom configurations you probably would not worry about whole

disk layouts on any system running B.11.11 (you need a 2GB or less disk drive to do this on PA-

RISC because of potential firmware limitations and HP-UX B.11.11 recommends at least a 4GB root

disk).

_hp_disk_layout == "Whole disk (not LVM) with HFS"

{

partitioned_disk

{

physical_volume disk[_hp_root_disk]

The file system partition on a partitioned disk must be HFS. It follows from the fact that the PA-RISC

boot loader can only read from some types of HFS file system (large files-enabled HFS file systems

cannot be booted from on PA-RISC systems). Therefore, the usage statement is set to be HFS. You

set the block size and the fragment size

to the HFS defaults defined earlier.

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.

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.