Ignite-UX Custom Configuration files

}
This code allows SD to select common and 64-bit only filesets (and not include 32-bit only filesets)
into the operating system. Because there is nothing similar for archives, you must do this manually.
Adding the non-SD application configuration file to the INDEX file
Now you can easily add the application configuration file to our cfg clause in the configuration
file using the following command:
# manage_index -a -f /var/opt/ignite/data/Rel_B.11.11/myapps_cfg \
-c "Custom B.11.11 installation using SD"
The software is now ready to install.
Installing patches from a depot
Installing patches from a depot is explained in the following three topics.
Setting up the depot
In this section, you will setup a depot containing the patches that you made sure were installed
earlier to enable the system to read the DVD containing the core operating system (OE) software.
At this point, you have a depot containing the patches that is observed using swlist:
# swlist -l depot
# Initializing...
# Target "test" has the following depot(s):
...
/var/opt/ignite/depots/Rel_B.11.11/patches_iso
# swlist -d @ /var/opt/ignite/depots/Rel_B.11.11/patches_iso
# Initializing...
# Contacting target "test"...
#
# Target: test:/var/opt/ignite/depots/Rel_B.11.11/patches_iso
#
#
# No Bundle(s) on test:/var/opt/ignite/depots/Rel_B.11.11/patches_iso
# Product(s):
#
PHCO_25841 1.0 Add Rock Ridge extension to mount_cdfs(1M)
PHKL_26269 1.0 Rock Ridge extension for ISO-9660
PHKL_28025 1.0 Rock Ridge extension for ISO-9660
Unfortunately, Ignite-UX does not work with products and filesets so you must package the product
patches into bundles.
Packaging the patches into a bundle
Previously the use of the make_bundles command to package products into bundles was
discussed; see "Package an application in SD format". The following command quickly places the
patc
hes into a bundle:
187