Users sometimes modify the configuration files for your product. Typically, these modifications are made to reflect site- and machine-specific information. It's important that you identify all the configuration files in your product so that modifications users made to older versions of these files are not lost during installation on the new versions.

By checking the config attribute check button, you identify the selected file as a configuration file. You must then specify a configuration type to specify how to deal with each configuration file. There are three configuration types. The first configuration type, update, is listed on the large button located to the right of the config attribute. Click this button to see all three choices, then select the appropriate configuration type from the list.

After you've selected a configuration type, click the Assign arrow button to assign the attribute to the selected file.

Here are the three configuration types:

The configuration types are listed below in a table that describes what Software Manager does with each type of configuration file.

Very few applications need this attribute—in general, don't select it. Selecting the shadow attribute delays the installation of the specified file until the next time the workstation is booted. So, Software Manager does not immediately install the file on the users' workstations.

This attribute is useful for products that might be used by a variety of applications at any given time—such as shared libraries—where a replacement of the existing product files might affect those applications that are using the product at the time a new version of the product is installed.

After selecting this attribute, click the Assign arrow button to assign the attribute to the selected file.

You can specify lists of commands that are to be executed during the installation of the selected file. The three types of lists and when they are executed are:

Although preops, postops, and exitops provide the flexibility to perform many types of processing at installation time, you should limit their use for these reasons:

To specify a list of commands for execution during installation, follow these steps:

---

Note: When saving your preop, postop, and exitop commands into the IDB file, swpkg converts any new lines into semicolons. When you start a new session with this IDB file, swpkg converts the semicolons back to new lines. So, when you type in your commands, you need to put a backslash in front of all “real” semicolons, to tell swpkg that you really do want a semicolon and not a new line.

---

It's a good idea to include an exitop to install your application's icon into the Icon Catalog. To do this, you would select your executable file and type into the exitop text field:

"tag tagnumber filename
iconbookedit -add 'Category:File Name:filename' -syspage whichPage
cd /usr/lib/filetype
make -u"

tagnumber is the number you're assigning to the application, filename is the name of the application, and whichPage is a particular page in the Icon Catalog. The last two lines update the Desktop database to include your changes. For an example of how to use the exitop attribute to add your application's Desktop icon to the Icon Catalog, see “Step Six: Adding Attributes”. For a more detailed discussion of the iconbookedit command, see the iconbookedit(1M) reference page or Chapter 15, “Adding Your Application's Icon to the Icon Catalog,” in the Indigo Magic Desktop Integration Guide. For instructions on tagging your files, see “Step One: Tagging Your Application” in Chapter 11 of the Indigo Magic Desktop Integration Guide.

When your software product is “installed” on a diskless workstation, each file is installed on a server in the share tree by default. This means that just one copy of each file is installed on the server and that copy is used by all diskless clients of that server. Your product may contain files that need to be duplicated for each client, typically because they are configuration files that must be modified for each client workstation.

To indicate that a file is to be replicated for each diskless client, select the noshare attribute from the Attribute Viewer. After selecting this attribute, click the Assign arrow button to assign the attribute to the selected file.

By default, swpkg automatically strips all binaries. You can override this behavior by selecting the nostrip attribute from the Attribute Viewer. After selecting this attribute, click the Assign arrow button to assign the attribute to the selected file. (See the strip(1) reference page for more information.)

In most cases, the files you include in your software product are applicable to all models of Silicon Graphics workstations. However, swpkg does provide a mechanism for restricting the installation of files to particular models on a per-file basis. You can use this mechanism to prevent users from installing files on a workstation that can't run them (which is better than allowing users to install files that won't work properly).

You'll need to set up installation restrictions if:

To restrict installation to specific models, you use the Machine Dependent (mach) attribute. By selecting the mach installation attribute for a file, you tell swpkg that the file is machine dependent. You then select the models that the file should be installed on from the mach attribute option list—the full mach attribute option list is shown in Figure 6-3.

The mach attribute option list is divided into three sublists:

CPUBOARD		The CPUBOARD sublist allows you to specify the types of CPU board with which the selected file is compatible. This sublist provides two buttons that allow you to automatically select either all the R3k boards or all the R4k boards. When you click one of these buttons, all the CPU boards of that type are automatically selected. You can still make further CPU board selections and deselections by clicking the check button corresponding to a particular CPU board. Note: The R4000 boards include derivatives of the R4000 architecture, such as R4400.
GFXBOARD		The GFXBOARD sublist allows you to specify the graphics boards with which the selected file is compatible. If you've already made selections from the CPUBOARD sublist, some of the boards in the GFXBOARD list may be disabled (grayed out). The disabled items correspond to graphics boards that are available only with the CPU boards you did not select.
SUBGR		The SUBGR sublist allows you to specify the types of subgraphics board with which the selected file is compatible. If you've already made selections from the CPUBOARD sublist, some of the boards in the SUBGR list may be disabled (grayed out). The disabled items correspond to subgraphics boards that are available only with the CPU boards you did not select.

Table 6-2 lists by machine type the CPU board, the graphics board, and the subgraphics board for many Silicon Graphics systems.

To restrict the models of workstations on which Software Manager can install a file in your product (by specifying those models on which the file can be installed), follow these steps:

To get the values for CPUBOARD, GFXBOARD, and SUBGR for a particular workstation, use the hinv(1M) command. This command gives you an output that looks something like this:

1 33 MHZ IP12 Processor
FPU: MIPS R2010A/R3010 VLSI Floating Point Chip Revision: 4.0
CPU: MIPS R2000A/R3000 Processor Chip Revision: 3.0
On-board serial ports: 2
On-board bi-directional parallel port
Data cache size: 32 Kbytes
instruction cache size: 32 Kbytes
Main memory size: 32 Mbytes
Integral Ethernet: ec0, version 0
CDROM: unit 4 on SCSI controller 0
Tape drive: unit 3 on SCSI controller 0: DAT
Disk drive: unit 2 on SCSI controller 0
Disk drive: unit 1 on SCSI controller 0
Integral SCSI controller 0: Version WD33C93A, revision 9
Iris Audio Processor: revision 3
Graphics board: GR2-Elan

To find out whether the workstation has an R3k or an R4k processor, look at the line that starts with “CPU.” In this example, hinv lists an R3000 (R3k) processor.

For more information on the type of CPU board, look at the first line of the hinv output. In this example, hinv lists an IP12 processor.

The hinv output provides graphics board and subgraphics board information using a different terminology than is used in the GFXBOARD and SUBGR sublists. To determine the values for GFXBOARD and SUBGR from hinv output, first look at the line labeled “Graphics board.” The IRIS Software installation Guide provides a table that maps the hinv output for each type of graphics board to the corresponding GFXBOARD and SUBGR values.

Since new values of CPUBOARD, GFXBOARD, and SUBGR may have been added for new models of workstations released after the IRIS Software Installation Guide was published, always check the most recent Release Notes for System Software to see if there is a more recent list of the possible values of CPUBOARD, GFXBOARD, and SUBGR.

---

Note: When you make selections of mach attributes, some of the buttons in the lists may appear disabled (“grayed out”). This prevents you from selecting a combination of options that do not correspond to an available Silicon Graphics architecture configuration.

---