##

##Note:

##This example shows the use of an NFS mounted directory

##from the Ignite-UX server to the client in order to obtain

##access to the archives. You could also use the ftp_source or

##remsh_source keywords instead.

##

##In order to use the nfs_source keyword as shown, you must first

##export the directory given in the nfs_source keyword. This is

##accomplished by editing the Ignite-UX server file /etc/exports

##and adding the export information. When editing is complete,

##be sure to run the "/usr/sbin/exportfs -av" command (as root)

##to make the take effect.

##

##See also:

##

-

instl_adm(4)

for

syntax documentation

##

-

instl_adm(1M)

for

checking syntax (-T option)

##- archive_impact(1M) for generating "impacts" statements

## - ignite(5)for general overview

##

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

The sw_source stanzas define the location of the archives that you want to reference using sw_sel clauses. In the following excerpt, the source format is set to archive so Ignite-UX will search the archive definitions in the sw_sel clauses that use this sw_source.

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

##Software Sources

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

sw_source "Per-Discipline Packs" {

description = "Software Apps for Individual Disciplines" source_format = archive

source_type = "NET"

#Change this to be your NFS server's IP and path: nfs_source = "14.12.99.113:/var/opt/ignite/archives"

}

The software categories, sw_category are defined next. Categories are a good way of grouping software together though if you create too many categories it may become more difficult to find software in the Software tab of the Ignite-UX GUI rather than easier. The following excerpt is an example of a sw_category definition:

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

##Software Categories

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

sw_category "Disciplines" {

description = "Software for Individual Disciplines"

}

Next is a test of the hardware model string. The expression is set to 9000/* meaning that if the string returned contains 9000 followed by zero or more slashes (/) then the first set of software defined in the following excerpt is for PA-RISC systems only. The software definitions that follow the else are for Itanium®-based systems.

184