Using noncore.cfg to define applications

Ignite-UX provides a template that you can use to define non-SD (archive based) applications in the file /opt/ignite/data/examples/noncore.cfg. The following is an excerpt from this file:

###########################################################

##

## Filename: noncore.cfg

##

##@(#) noncore.cfg $Revision: 10.10 $

##Description:

##

The template file provides a description of itself and how you can use it to define non-core operating system software installations.

##If the software source is not an "SD" depot, then the

##make_config command cannot be used to generate a config file

##to represent it and therefore the config file would have to

##be manually created. This example gives a starting template

##to use for such a config file.

##

##This config file would be used for a non-coreOS (application)

##tar/cpio archive.

##

When you copy this file do not make the name noncore.cfg, rather rename it to a name that allows you to observe what application it is defining. The following excerpt describes this concept:

##This config file should be copied to:

##/var/opt/ignite/data/Rel_B.<release>/<filename>

##then edit this new file to match your situation.

##The values that you will most likely need to change in this

##new file are:

##

nfs_source - IP address and directory

path to server

##

directory containing the

archives.

##archive_path - path name of archive to be loaded from the

##

sw_source

-

nfs_source location.

##

tag

name

of

the

software source.

##

sw_sel

-

tag

name

of

the

software select.

##description - description of software.

##

impacts

- amount of space needed, for a given selection,

##

 

on each named file system.

##

 

 

##Also, you may need to:

##- add or delete any sw_sel's you do not need.

##- run /opt/ignite/lbin/archive_impact on each

##archive and replace the "impacts" statements with

##those given by the archive_impact tool.

##

##

##When done editing this config file, be sure to run:

##/opt/ignite/bin/instl_adm -T -f <filename>

##to check for syntax errors. Then either use manage_index, or

##manually edit the /var/opt/ignite/INDEX file to add a reference

##to the copy of the file you edited.

183