IMPORTANT: The first 8 KB of the install file system ([WVI]INSTALLFS) can contain Ignite-UX configuration content. If it does, this information is used first and can override configuration statements in the LIF INDEX and CONFIG files. If the tape contains a golden archive, you will want to consider whether the tape must contain special config content to control system setup in some custom way. If the golden archive will be used with different system configs, conditional expressions can be used to adapt the config appropriately, such as run_ui, which controls whether the installation is interactive or not, and server and sd_server, which can be used to control network installation. See instl_adm(4) for more information.

Archives and depots

The LIF volume is followed by the first archive (a golden archive or a recovery archive depending on the purpose of the media) or is empty if the installation is solely from a software depot.

The first archive is then followed by either a serial depot or another archive. There can only be one serial depot on a tape, and it must be the third file on the tape. If the tape includes a serial depot, the make_config command must be used to create the config file for the depot content. This configuration file is then modified to reflect the final destination of the depot and the depot is written to the tape.

The previous files can be followed by one or more additional archives, limited only by the capacity of the tape. These archives are optional.

TIP: If a tape will contain multiple archives, you might want to place the most commonly used archive first so installations take less time.

Creating and modifying an archive configuration file for tape

Create the archive configuration file — Proceed as described in Chapter 11 (page 151) or Chapter 15 (page 191), depending on the usage of the installation tape.

Modify the archive access attributes — Change the following archive access attributes in the sw_source core clause:

•Find the source_type attribute and change the value from NET to MT (for example, source_type=MT).

•Find the change_media=FALSE attribute line and remove the comment hash mark ( #).

•Find the nfs_source attribute line and place a comment hash mark before it (for example,

#nfs_source=).

The above edits change the source type from network (NET) access (which is NFS, ftp or remsh) to magnetic tape (MT). Since the archive is going to reside on the same media as the configuration file, change_media is set to FALSE by uncommenting that attribute. To stop the NFS mount attempt, the nfs_source attribute is commented out.

Modify the archive path and impacts — In the HARDWARE_MODEL ~ 9000.* clause:

•Find the archive_path attribute and set the value to the number of EOF markers that have to be skipped to get to the archive (archive_path=n). There is an EOF marker after the LIF volume, archives, depots, and empties. For example, to reach the first archive on the tape, the archive_path would have to be set to “1”, indicating the LIF volume EOF would be skipped and the archive begins thereafter.

•Find the impacts attribute with the value / 27KB and change the value to what is reported by archive_impact.

•Optionally, you can find the sw_sel and description attributes and change their values to something more descriptive and applicable for your situation. These modified values are visible on Basic tab of the Ignite-UX GUI.

182 Creating your own boot and installation media