User's Guide

HP-UX Release

PA-RISC Itanium®-based

B.11.11 B.11.11 N/A

B.11.23 B.11.23 B.11.23

B.11.31 B.11.31 B.11.31

Ther

efore, if you boot the B.11.11 installation kernel you can install HP-UX B.11.11 but you cannot

install B.11.23. The reverse applies - if you boot the B.11.23 PA-RISC installation kernel, you

cannot install B.11.11 with it.

When you create custom configuration files and do not plan to include the default configuration

files you must set this variable.

release="B.11.11"

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

Some time ago, changes were made to Ignite-UX to increase the block and fragment sizes for VxFS

and HFS file systems. This can lead to differences between systems installed in the last few years

and much older systems that had smaller default block and fragment sizes (for example, the file

system attributes are different so the block and fragment sizes from older systems are probably

smaller).

The use of <variable> visible_if false ensures that the variables do not appear in the

Additional dialog box from the Basic tab.

init _hp_HFS_blksize = 65536 # HFS block size.

init _hp_HFS_fragsize = 8192 # HFS frag size.

init _hp_VxFS_blksize = 8192 # VxFS block size.

init _hp_FS_stripe_size = 64Kb # File system stripe size.

_hp_HFS_blksize visible_if false

_hp_HFS_fragsize visible_if false

_hp_VxFS_blksize visible_if false

_hp_FS_stripe_size visible_if false

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

The following example shows the start of a definition for the _hp_disk_layout variable, which is

set to one of four possible values.

Around the _hp_disk_layout is a test for is_hppa (is PA-RISC). This only exists in this file since

the file is generated from one common source file using unifdef (refer to unifdef(1) for more

information) for all HP-UX releases. Obviously, this test is not actually needed for HP-UX B.11.11

since it is only supported on PA-RISC systems. The entire release-specific configuration files are

based on one original file and they are processed with unifdef to produce the release-specific

configuration file.

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

HP-UX release of the install kernel