HP 9000 Manual page 160

Using Configuration Files
Introduction
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] {
}
physical_volume disk[2/0/1.4.0] {
}
logical_volume "apps1" {
mount_point= "/apps1"
usage=VxFS
size=30%free
minfree=5
stripes=2
}
logical_volume "apps2" {
mount_point= "/apps2"
usage=VxFS
size=remaining
minfree=5
stripes=2
}
}
This example defines a few of the network parameters which will be
assigned to the machine after it has been installed:
final system_name = "acorn1"
final ip_addr["lan0"] = "15.99.45.123"
final netmask["lan0"] = "255.255.248.0"
final nis_domain = "nis1"
final route_gateway[0] = "15.99.45.1"
This example defines a single SD depot from which software can be
installed. Two different pieces of software are defined for the SD depot.
Each can be selected independently for installation. The impacts lines
tell Ignite-UX how much space this software requires in a given
directory. This information is used to size the file systems correctly.
Another interesting construct is sw_category. This allows you to group
the software so that the user interface can present it in chunks which
make sense to you. Since this example references an SD depot, it would
have been created by the make_config command:
sw_source "ee_apps_depot" {
description = "Electrical Engineering Application"
source_format = SD
source_type = "NET"
sd_server = "15.23.45.6"
sd_depot_dir = "/var/opt/ignite/depots/Rel_B.10.20/ee_apps"
}
160 Appendix B