Using Golden Images with Virtual Partitions

8
The line of most interest is the one containing the
golden_image_cfg, which is the
configuration file we added in the previous step. The config and config.local files
contain default configurations.
The
/var/opt/ignite/config.local file should be the last file in the cfg stanza. The last
configuration file has the highest priority and can override values in the
configuration files listed before it.
The file
/opt/ignite/data/Rel_B.11.23/config supplies the disk and file system layout
defaults, along with other control information required by Ignite-UX. It must be first
in every cfg stanza.
Each configuration stanza appears as an available configuration to Ignite-UX.
Therefore, the string “HP-UX B.11.23 PA Golden Image Archive” now
appears as a valid configuration.
Step 4. Verify that the /var/opt/ignite/INDEX syntax is correct:
/var/opt/ignite/bin/instl_adm -T
Fix any errors found by instl_adm, and execute the command again to verify any
changes.
Step 5. Ensure that the NFS file system is exported correctly. In the sw_source stanza
in the example in the previous step, we specified the location of the operating
system archive to be a file on an NFS server. You need to ensure clients have
access to this directory.
Make sure the NFS configuration is correct. To view the current status and ensure
the directory containing the archive is correctly exported, enter:
exportfs –v
Ignite-UX automatically tries to export /var/opt/ignite/clients for its use. In our
example, /var/opt/ignite/archives/Rel_B.11.23 must also be exported because that is
where we placed the operating system archive. Here is our /etc/exports file:
/var/opt/ignite/clients -anon=2
/var/opt/ignite/archives/Rel_B.11.23 -ro,anon=2
If you added new content to the /etc/exports file as above, re-export it as follows:
exportfs –av