Installing HP-UX 11.0 and Updating HP-UX 10.x to 11.0 HP 9000 Computers Edition 1

Appendix B 225
Using Configuration Files
Combining Config Files Via INDEX Entries
in the first 8 KB of /opt/ignite/boot/INSTALLFS is implicitly appended to
each configuration. The client-specific configuration file
(/var/opt/ignite/clients/0x{LLA}/config) is implicitly added as
the last config file for each configuration.
A default cfg clause for each release is shipped as part of the Ignite-UX
product. Additional cfg clauses are added when the following apply:
• You save a named configuration from the graphical user interface via
the Save As button.
• You wish to create a configuration by modifying the INDEX file
directly
Examples of Config files
This section shows a few sample config files to give you an idea of their
look and capabilities. It does not pretend to fully cover the subject. See
the instl_adm(4) manual page for a complete description.
The following example shows how a disk might be defined. Here, the disk
is located at hardware address 2/0/1.6.0 and does not use LVM. The disk
contains the "/" file system and a swap area. The swap area takes up 64
MB, and the file system takes up whatever space is left over:
partitioned_disk {
physical_volume disk[2/0/1.6.0] {
}
fs_partition {
mount_point ="/"
usage=HFS
size=remaining
file_length=long
}
swap_partition {
usage=SWAP
size=64Mb
}
}
In this example, two disks are put together to form a single LVM volume
group. Two file systems are defined; both are striped across both disks.
The first file system ("/apps1") is sized by calculating the amount of
space required by the software which is to be loaded, and then adding a
30% free space cushion. The second file system ("/apps2") gets all of the
remaining space on the disks.
volume_group "appsvol" {
physical_volume disk[2/0/1.5.0] {
}