User's Guide
In summary y
ou can use:
save_file to keep the version of the file from the Operating System archive preventing Ignite-
UX from making changes to the file;
merge_file to keep the version of the file from the Operation System archive but allow Ignite-
UX to make customizations to it based upon the configuration for the installation session.
Creating a golden image
The creation of a golden image is not discussed in this document. For more information, see
make_sys_image(1M) and the Ignite-UX Administration Guide.
It is important to realize that a golden image is an archive created by make_sys_image at clean
level 2 (make_sys_image -l 2) so it contains no host-specific information where possible. You
should not call a make_net_recovery or make_sys_image archive created at any other clean
level for a golden image. In other words, to be a golden image, the archive must be created at
clean level 2 using make_sys_image.
Final words about golden image installations
If you look at the example cfg clause from the /var/opt/ignite/INDEX file described in the
core11.cfg file, you can see similarities between it and the SD-based cfg clause:
cfg "HP-UX via an OS archive" {
description "11.11 system using archives."
"/opt/ignite/data/Rel_B.11.11/config"
"/opt/ignite/data/Rel_B.11.11/core11.cfg"
"/var/opt/ignite/config.local"
}
Both clauses include the release-specific configuration file config before any other configuration
files are defined. Then the configuration file that defines the location of the core operating system
(OE) is defined.
Because config.local must always be loaded last, you can see that after the entry for
core11.cfg is the point at which you would begin adding additional configuration files to install
other software like patches, additional applications, and customizations.
With virtually no changes, the contents, and methods explained in the "Installation configurations
usin
g Software Distributor depots" section can be used here. This is because the name of the core
operating sy
stem sw_sel will change so some small changes are required if you have
corequisites, exrequisities, or other dependencies on this name
89
).
89
The SD-based installation examples include a dependency between an application and which of the sw_sels, HPUXBase32 or
HPUXBase64,was selected. This would change to be based upon the sw_sel name of the core operating system (OE) golden images.
202