Ignite-UX Custom Configuration files

## - remove any extra sw_sel clauses.
## - run /opt/ignite/lbin/archive_impact on each OS archive
## and replace the "impacts" statements with those given
## by the archive_impact tool.
##
## - Edit the /var/opt/ignite/INDEX file. If you already have a
## stanza in the INDEX file that refers to an SD depot, then
## you will probably want to make a new stanza ("cfg" clause)
## that does not have references to the core SD cfg files, and
## insert the path to your newly edited configuration file.
## The end result should look something like this:
##
HP recommends that /opt/ignite/data/Rel_B.xx.yy/config is included first, similarly
with SD installs there is information already defined that allows you to start with a very strong
configuration that you can customize for your environment.
It is easiest to begin customizing by renaming core11.cfg to a new name and placing it in
/opt/ignite/data/Rel_B.xx.yy/config. It is likely that you will have more than one
golden image installation defined for any one HP-UX revision so customizing core11.cfg directly
is not recommended.
## 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"
## }
##
## - If you have additional archives or applications in an SD
## depot that you would like loaded along with this archive,
## you may create a configuration file for them and add it to
## the INDEX file entry as well.
##
## See make_config(1M) for creating configuration files for an
## SD depot. See the example file "noncore.cfg" for setting
## up application archives.
##
## - After making changes, always run:
##
## # /opt/ignite/bin/instl_adm -T
##
## to check the syntax.
##
########################################################################
########################################################################
## Software Sources
########################################################################
In the sw_source clause for the core operating system archive, the source format is archive so
sw_sel definitions that use this sw_source must be archives as well. Since this archive contains
the core operating system, it must be loaded at load order zero (0)
87
.
87
Only one archive can be loaded at load order zero (0), and it must be the core operating system archive. For technical reasons if the core
operating system archive cannot fit within a certain size (cannot be written to a CD) then you must attempt to split out the software that can be
loaded after load order one. For example, /opt.
196