Technical data

Appendix A 91
Sample Configuration File
# Load the ASX bundle from a different depot during the
# post config phase (in addition to other post_config_cmd).
post_config_cmd += "
swinstall -s 15.1.54.112:/asx B3782CA_ABJ"
# For LVM configurations, adjust the volume size
# for /var and create a /extra volume:
"Disk Layout:Logical Volume Manager" {
volume_group "vg00"
{
logical_volume {
mount_point = "/var"
usage = HFS
size = 100Mb
nbpi = 2048
"File system file name length:Short" {
file_length=short
}
}
logical_volume {
mount_point = "/extra"
usage = HFS
size = remaining
}
}
}
}
# Define a new software selection that will appear along with
# with other software selections. Note that the software language
# specification will be ignored when this is selected.
"Software Selection:Software config for our office."
help_text "This is a custom software selection that selects only what
our office needs. (Desktop, ANSI-C, and our own software)"
"Software Selection:Software config for our office." {
sd_software_list = "
Product_Name
Product_Number
OurSW
"
}
When a system is installed, the configuration that was selected for that
system is stored in the /usr/lib/sw/hpux.install/config.local file. A
system that is configured as a network cold-install server will provide its
own configuration to its clients as an option from which the the user can
select.
It is also possible to concatenate another system's config.local file to that
of the server's in order to have multiple configurations available to
clients. Alternatively, the config.local file may be hand-crafted (as shown
in the previous example) to make slight modifications to the default
configuration.