1    Installation Overview and Preinstallation Tasks

This chapter includes the following information:

• Quick start information for experienced users

• A description of the two types of software distribution media

• A description of the two user interfaces

• Preinstallation tasks

• Minimum firmware revisions for all supported processors and single-board computers

• Hardware configuration utilities

• A description of the types of installation procedures: update, full, and cloned

• A description of the UNIX shell option

• A summary of the full installation process

• What to do if your system was delivered with preinstalled software

• How to install worldwide language support software

The goal of this chapter is to provide the information necessary for you to perform the user actions shown in Table 1-1.

Table 1-1: Summary of User Actions

1.1    Quick Start for Experienced Users of the Full Installation

If you are an experienced user of the Digital UNIX operating system, you should read overview information in this chapter. The Digital UNIX Version 4.0 installation procedure has two new user interfaces that you may want to read about before beginning. After reading the overview information in this chapter refer to Table 1-2 for quick start instructions.

The following statements qualify you as an experienced user:

• You have previously performed a full installation and are familiar with the decisions required to perform a full installation. Be aware that in Version 4.0 the installation types have new names. The installation types previously known as basic and advanced are now called default and custom respectively.

• You know whether you are using CD-ROM or RIS as the distribution media.

• You know the type of installation you want to do.

• You know the disks and partitions you want to use for the root, /usr, and /var file systems and for swap space.

• You know whether or not you want to install optional software subsets.

If most of the previous statements are true, refer to Table 1-2, which provides the steps to get you started quickly.

Table 1-2: Full Installation Steps for Experienced Users

If you want to perform an update installation and you are an experienced user, go directly to Chapter 2.

If you are not an experienced user, Digital recommends that you read this chapter in its entirety.

1.2    Software Distribution Media

There are two types of distribution media you can use to install the Digital UNIX base operating system:

• From the Digital UNIX CD-ROM labeled Digital UNIX V4.0 Operating System Volume 1 that contains Digital UNIX Version 4.0. The software subsets contained on this CD-ROM are described in Appendix C.

• Over a network connection to a remote installation services (RIS) server that is serving Digital UNIX Version 4.0 .

Deciding which distribution media to use for the installation depends on the following:

• If you have a copy of the Digital UNIX CD-ROM labeled Digital UNIX V4.0 Operating System Volume 1 in your possession and your system has a CD-ROM drive, you can perform the installation from CD-ROM.

• If your site has a RIS server that is capable of serving Digital UNIX Version 4.0, ask the RIS server administrator if you should perform a RIS installation. The RIS server administrator performs the tasks necessary to register your system as a client of the RIS server.

• If you are the RIS server administrator and want to perform a RIS installation, follow the instructions in Sharing Software on a Local Area Network to learn how to set up a RIS server and how to register clients.

1.3    Types of User Interfaces: Graphical and Text Based

Two user interfaces are available for the Digital UNIX full installation process:

• A graphical interface

• A text-based, menu-driven interface

The type of interface presented during the full installation is determined automatically based on your hardware configuration and the amount of memory on your system. Systems with graphical consoles and a minimum of 32 MB of memory present a graphical interface to the installation. Systems with consoles that do not have graphics capabilities or have less than 32 MB of memory present a text-based interface.

While you are entering information during the installation setup phase, the graphical and text-based interfaces record your responses in a configuration description file (CDF). The installation procedure uses the information stored in the CDF to configure disk and file systems and to install the selected software subsets. After the installation, the CDF is located on the newly-installed system in /var/adm/smlogs/install.cdf.

If the CDF generated from an installation is copied to a remote installation services (RIS) server, the CDF can be used to clone another system with a similar hardware configuration. The RIS administrator is responsible for setting up a system for a cloned installation. Refer to Section 1.5.4 for a description of cloned installations.

Table 1-3 lists the common attributes of the two user interfaces.

Table 1-3: Common Attributes of the Graphical and Text-Based Interfaces

1.4    Preinstallation Tasks

Table 1-4 summarizes the preinstallation tasks to complete before beginning any software installation.

Table 1-4: Summary of Preinstallation Tasks

Note

If you plan to run your system as a dataless client of a DMS server, consult your RIS server administrator or Sharing Software on a Local Area Network. On a dataless client, the root and /usr file systems are located on a dataless server and are exported to your system. You do not need the instructions in this book to run your system as a dataless client.

The following sections describe the preinstallation tasks to complete before invoking the installation procedure.

1.4.1    Check the Hardware for Installation Readiness

Ensure that you have the hardware needed for an installation. You must know the location and function of the controls and indicators on your hardware. Verify that all cables and connectors are hooked up and that the system is plugged in. Refer to your hardware owner's documentation for more information.

You need some or all of the following items to install the Digital UNIX operating system software:

• Your system must have a CD-ROM disk drive if you are installing the software from the Digital UNIX CD-ROM distribution media

• Disk for the root file system (required)

  You need at least one supported disk to contain the root and /usr file systems and swap space. You will use this disk to boot your system after the installation. If you perform a custom installation, you can allocate the /usr and /var file systems and swap space to disks other than the disk that contains the root file system. Refer to Section 3.4 for more information about supported disks.

• Data disks (optional)

  A data disk is a disk on which data and user files are stored and on which no Digital UNIX file system resides. The installation procedure does not configure these disks.

• Console terminal (required)

  The console terminal communicates with your system during the installation.

• Network capabilities if you are planning to perform the installation using the remote installation services (RIS).

1.4.1.1    Configuring ISA Devices Before the Installation

The information in this section applies only if your system has an Integrated System Architecture (ISA) bus (most AlphaServers and AlphaStations).

If you plan to connect ISA devices to your system (for example, floppy controllers, graphics cards), use the isacfg console command to supply the appropriate configuration information.

The isacfg console command is available on systems that have an ISA bus. There is information about the command in the user documentation for each of the systems that support ISA bus devices. If you need to know more about the format of the command, enter

>>>  help isacfg

The System Reference Manual (SRM) console firmware provides information about the ISA bus devices that come configured with Digital systems as well as the device handles that are set up. Use the following console firmware command to view this information:

>>>  isacfg -all

When you specify a device with the isacfg command, you must use a handle as the name of the device. The following table lists the handles for optional ISA devices that you can configure for your system.

Table 1-5: Optional ISA Device Handles

Table Note:

1. If you configure generic VGA graphics, you must reset the graphics device to the handle defined by the vendor just before rebooting the system so that Xwindows recognizes the device. Section 5.18 provides the instructions to do so where applicable in the installation procedure.

2. A kernel device driver kit is any graphics kit that is not supplied by the Digital UNIX base operating kit. If you are performing a RIS installation from a RIS area that has the required graphics kit already installed, the handle for isacfg should be set to the handle specified by the vendor.

Use the -handle handle-name flag to specify the device handle. The following example sets the parameters for configuring the DE205 Ethernet controller. When you issue such a command, let the input line wrap; do not press the Return key in the middle of the line:

>>>  isacfg -slot 1 -dev 0 -mk -handle DE200-LE -irq0 5
   -iobase0 300 -membase0 d0000 -memlen0 10000
   -etyp 1 -enadev 1

See your hardware documentation for more information about ISA configuration.

1.4.1.2    Installing ATM Adapters Before the Installation

The information in this section applies only if you plan to use Asynchronous Transfer Mode (ATM) adapters.

You should install the DGLTA ATM adapter before installing Digital UNIX Version 4.0 so that the installation procedure properly detects the presence of the ATM adapter and automatically installs the ATM software subsets. If you install the ATM adapter after installing Digital UNIX, you must boot the system using the generic kernel /genvmunix, install the ATM software subsets from the CD-ROM or RIS server, and then run the doconfig program to rebuild your system kernel to enable the added ATM support.

1.4.1.3    Installing on SCSI RAID Devices

If you are installing the Digital UNIX operating system on a SCSI RAID device, only LUN 0 can be used for the installation's target device. The RAID device's LUN 0 must be configured before you attempt to install the software. Refer to Section 1.4.7.2 for more information about RAID devices.

1.4.2    Check the Software Distribution Kit

You should have received a Software Distribution Kit that contains, among other items, the Digital UNIX CD-ROMs. A Part Listing is included in the box and lists the contents of the Software Distribution Kit . At a minimum, the Software Distribution Kit contains the following CD-ROMs and documents:

• Three Digital UNIX CD-ROM optical discs:

  • The Digital UNIX base operating system software CD-ROM labeled Digital UNIX V4.0 Operating System Volume 1

  • The additional software products CD-ROM labeled Digital UNIX V4.0 Associated Products Volume 1

  • The documentation CD-ROM labeled Digital UNIX V4.0 Documentation Volume 1

• The firmware update CD-ROM labeled Alpha Systems Firmware CD-ROM Version 3.5

• The firmware release notes Alpha AXP Systems Firmware Update Release Notes Overview

• This guide, the Installation Guide

• The Release Notes

• The Technical Overview

• The Digital UNIX Software Product Description (SPD)

1.4.3    Check Network Connections for RIS Installations

If you have a RIS server at your site, ask the RIS server administrator whether or not you can perform a RIS installation.

You need a connection to the network (via Ethernet, Token Ring, or FDDI) and to a RIS server if you plan to perform a Remote Installation Services (RIS) installation over a local area network (LAN). Refer to your hardware installation guide for information about network connections.

If you are installing over a network connection to a RIS server, follow these steps:

1. Your machine must be registered as a client of a RIS server that is serving Digital UNIX Version 4.0 . If your RIS server administrator has set up your system for a cloned installation, ask the RIS server administrator to ensure that your system is registered to the appropriate RIS environment and configuration description file (CDF). Section 1.5.4 describes a cloned installation.

2. If your system is already running a version of Digital UNIX, ensure your system can communicate with the RIS server by executing the /sbin/ping command to verify the network connection. Enter the command in the following format and replace server with the name of your local RIS server:

   #  /sbin/ping -c2  server
   

   Successful output of the /sbin/ping command is similar to the following:

   # ping -c2 system9
   PING system9 (16.59.l24.96): 56 data bytes
   64 bytes from 16.59.l24.96: icmp_seq=0 ttl=255 time=1 ms
   64 bytes from 16.59.l24.96: icmp_seq=1 ttl=255 time=0 ms
   
    
   
   ----system9 PING Statistics----
   2 packets transmitted, 2 packets received, 0% packet loss
   round-trip (ms)  min/avg/max = 0/0/1 ms
   

   In the previous example, system9 is the name of the RIS server.

   Your system is not able to communicate with the RIS server if you obtain the following results from the /sbin/ping command:

   • Only your system name and IP address is displayed if the name server recognizes your system name but the network connection is not set up.

   • The message Unknown host is displayed if your system does not recognize the RIS server name.

     If you obtain the previous results, ask the RIS server System Administrator to troubleshoot the problem.

Refer to Sharing Software on a Local Area Network for more information about RIS.

1.4.4    Read the Digital UNIX Release Notes

Read the Digital UNIX Release Notes before beginning any software installation procedure. The Release Notes document any last-minute changes to the software. This information might be required for a successful installation.

The Release Notes also provide descriptions of features that are new to the Digital UNIX Version 4.0 operating system or have changed significantly from previous releases.

A printed version of the Release Notes is included in the Digital UNIX Software Distribution Kit you received.

1.4.5    Back Up the System

This step applies only if your system is already running the Digital UNIX operating system and you have critical files that you want to preserve.

Before you begin any software installation procedure, Digital recommends that you perform a full back up of your current operating system. Refer to System Administration for information about backing up your system.

1.4.5.1    Special Considerations for Systems Running LSM, LVM, Prestoserve, and AdvFS

If your system is currently running Digital UNIX and is using the Logical Storage Manager (LSM), the Logical Volume Manager (LVM), Prestoserve, or the Advanced File System (AdvFS), refer to Appendix A for special preinstallation backup tasks for these products.

1.4.6    Update System Firmware

Digital distributes console firmware for certain processors whenever the operating system is updated or as is required. To run Digital UNIX Version 4.0, your system might require a firmware update. Firmware updates are located on the Alpha Systems Firmware CD-ROM Version 3.5 compact disc that is included with your Digital UNIX Software Distribution Kit. Firmware updates for all supported processors reside on the firmware CD-ROM. The firmware revision level may be different for each processor.

The Alpha AXP Systems Firmware Update Release Notes Overview describes how to mount the firmware CD-ROM and how to print processor-specific firmware update instructions. To mount the firmware CD-ROM if your system is already running Digital UNIX, the kernel must be configured for the ISO 9660 Compact Disc File System (CDFS). The CDFS option must be present in the kernel configuration file to configure CDFS in the kernel. Refer to System Administration for more information.

Table 1-6 provides the minimum firmware requirements for processors running Digital UNIX Version 4.0.

Table 1-6: Minimum Firmware Revision Levels for Alpha Systems

1.4.6.1    Updating Firmware on AlphaPC64, EB64+, EB66+, and EB164 Single-Board Computers

The EB64+ single-board computer uses a socketed firmware ROM chip. The EB66+, AlphaPC64, and EB164 single-board computers use an EPROM that can be updated with new firmware. Refer to your hardware owner's documentation for details on how to update the console firmware on these systems.

1.4.7    Run Hardware Configuration Utilities

As described in the following sections, depending upon the type of hardware you have, you may have to run hardware configuration update utilities before the installation.

Hardware configuration diskettes are usually shipped with a system when you first receive it. If you do not have the appropriate diskette and did not receive one in the Software Distribution Kit, contact your local Digital sales office or the vendor from which you obtained the hardware.

1.4.7.1    Minimum EISA Configuration Utility (ECU) Firmware Revision Level

Before installing Digital UNIX on a system with an Extended Integrated System Architecture (EISA) bus, you must run the EISA Configuration Utility (ECU). Follow the instructions in your hardware owner's guide.

For Digital UNIX Version 4.0 software, the supported ECU firmware revision is 1.9 or higher. If your system is connected to an EISA bus you will receive a a floppy disk that contains the ECU. This floppy disk may be included in the Digital UNIX Software Distribution Kit.

1.4.7.2    Minimum RAID Configuration Utility (RCU) Revision Level

Before installing Digital UNIX on a system employing RAID technology, you must run the RAID Configuration Utility (RCU). Follow the instructions provided in your hardware owner's guide.

For Digital UNIX Version 4.0 software, the supported RCU revision level is 3.11 or higher. The RCU is included on the Alpha Systems Firmware CD-ROM Version 3.5.

1.4.7.3    Updating the Advanced RISC Computing (ARC) Console

Advanced RISC Computing (ARC) is an alternate console interface that was designed to support the Windows NT operating system. Some system configuration utilities may require you to switch to the ARC console. Refer to your hardware owner's guide for more information. To run Digital UNIX Version 4.0, you may need to update the console firmware. The ARC firmware update is included on the Alpha Systems Firmware CD-ROM Version 3.5.

1.4.7.4    Updating the System Reference Manual (SRM) Console

To run Digital UNIX Version 4.0, you may need to update the SRM console firmware. The SRM firmware update is included on the Alpha Systems Firmware CD-ROM Version 3.5. Refer to your hardware owner's guide for more information.

1.5    Installation Types: Update, Full, and Cloned

You can perform an update installation, a full installation which has default or custom procedures, or a cloned installation procedure to install the Digital UNIX Version 4.0 operating system.

Note

If you plan to run this system as a dataless client of a DMS server, refer to the Sharing Software on a Local Area Network guide for more information.

An update installation updates your operating system from Digital UNIX Version 3.2C, 3.2D-1, or 3.2D-2 to Digital UNIX Version 4.0. If your operating system predates Digital UNIX Version 3.2C, 3.2D-1, or 3.2D-2, you can perform successive update installations to reach Version 4.0.

A full installation affects many of the system files from the previous version of Digital UNIX . File systems and swap areas created during a full installation will overwrite existing data on disks and partitions where they are installed.

A cloned installation refers to the process of configuring file systems and installing software on your system exactly as another similar-type system is configured. A cloned installation can only be performed over a network connection to a remote installation services (RIS) server.

The following sections describe these types of installations.

1.5.1    Description of an Update Installation

An update installation updates the Digital UNIX base operating system from Version 3.2C, 3.2D-1, or 3.2D-2 to Digital UNIX Version 4.0. The update installation preserves user files, data files, print and network configurations, user accounts, and any other system setup and customization you may have done. Preserving this data is an advantage over the full installation because a full installation creates file systems and swap areas that overwrite any existing data on the disk partitions where the file systems and swap areas are to be installed.

You should not perform an update installation if you want to change file system type or change the location of file systems. An update installation does not permit changes to file systems or disk layout.

An update installation does not update optional layered products, but you can still perform an update installation if you have layered products installed. Some layered products operate properly with Digital UNIX Version 4.0 and others must be reinstalled with a version that is compatible with Digital UNIX Version 4.0. Some layered products, such as DECnet, must be deleted before the update begins and then reinstalled after the update completes. Section 2.5 provides a complete list of the layered products that must be deleted before the update installation.

Completion time varies depending on your processor type, the number of software subsets to be updated, whether you are using CD-ROM or RIS to perform the update, and the speed of your CD-ROM drive if you are using CD-ROM. You need to respond to prompts only during the initial phase of the update. After that, the update installation runs unattended.

The Common Desktop Environment (CDE) is the default desktop for Digital UNIX Version 4.0 and is installed automatically during the update installation.

If your system predates Version 3.2C, 3.2D-1, or 3.2D-2 you can do successive update installations to reach Version 4.0.

How do you start an update installation?

Follow the instructions in Chapter 2.

1.5.2    Description of a Default Installation

A default installation is a full installation that installs a default, mandatory set of Digital UNIX software subsets on a predetermined file system layout on a single disk. The only decision you have to make is what single disk will contain the root and /usr file systems and swap area.

The file system type for all file systems is the UNIX File System (UFS). One swapping area is configured; other swap areas can be added after the installation. Optional software subsets can be installed later by using the setld command. By performing a default installation, you can have your operating system running with a minimum amount of work because a default installation uses preset defaults for file system layout, file system type, and kernel build options. Following is the file system layout for a default installation:

• The root file system is on the a partition.

• The /usr file system is on the g partition.

• The var area is a directory in the /usr file system.

• The swapping area (swap1) is on the b partition.

How do you start a default installation?

Perform the prerequisite tasks described in

Section 1.4

Shut down your system to console mode (>>>) and boot the

system off the CD-ROM or RIS distribution media as shown in

Chapter 4.

1.5.3    Description of a Custom Installation

A custom installation is a full installation that lets you customize the file system layout and lets you select optional software to install. You can use one or more disks, and you have the option to configure a second swap area. You can choose the UNIX File System (UFS) or the Advanced File System (AdvFS) as the file system type for the root, /usr, and /var file systems. You may also choose additional kernel options to tailor your kernel for specific use.

Systems with less than 32 MB of memory do not have the option to select the Advanced File System (AdvFS) as the file system type for /root, /usr or /var.

In addition to installing the mandatory set of Digital UNIX software subsets, the custom installation lets you select optional software subsets to customize your system. Dependencies between optional software subsets are checked and resolved.

The amount of free space remaining in the root, /usr, and /var file systems is displayed as you select each optional software subset to install.

The graphical user interface provides access to the Disk Configuration Utility. This utility lets you repartition disks before or after you select optional software if the partition you chose is too small for a particular file system.

How do you start a custom installation?

Perform the prerequisite tasks shown in

Section 1.4

Read the disk planning information in Chapter 3 to decide

which disks and partitions to use for file systems and

then decide whether or not you should use the default disk

partitions or customize them.

Shut down your system to console mode (>>>) and boot the

system off the CD-ROM or RIS distribution media as described

in Chapter 4.

1.5.4    Description of a Cloned Installation

A cloned installation lets you duplicate the file system layout, file system type, and software subset selections from a system that has already been installed with Digital UNIX Version 4.0.

Your system is set up for a cloned installation by the RIS server administrator who registered your system to a RIS environment as well as to a configuration description file (CDF). CDFs are created during a full installation procedure, and the RIS server administrator manually copies the CDFs from an already-installed system to the RIS server's central CDF directory.

The cloned installation procedure retrieves the configuration description file (CDF) to which your system is registered from a directory of CDFs stored on your RIS server. A cloned installation procedure uses the same disks and partitions to create a file system layout and installs the same set of software subsets as defined in the CDF. If your system is set up to perform a cloned installation, you do not have to answer any installation questions related to disk and software selections because the answers are already stored in the CDF. The only question you have to answer is whether or not you want to continue the cloned installation procedure.

If you decide not to use the CDF, the installation procedure continues interactively. Before any changes are made to your system, the CDF is validated to make sure your system is compatible with the CDF. When CDF validation is complete, a cloned installation runs unattended (except for optional kernel selections if the CDF was originally created during a custom installation).

1.6    UNIX Shell Option

Both the text-based and graphical installation interfaces provide a way for you to access a UNIX shell. The primary purpose of the UNIX shell option is to provide a way to perform disk and file system maintenance before the installation and to perform disaster recovery tasks.

When you start a text-based, menu-driven installation, the UNIX shell is presented as an option from the first menu. If you are using the graphical interface, you access the UNIX shell from a button labeled UNIX Shell. Regardless of the interface, this option puts your system into a Bourne shell in single-user mode with superuser privileges. To restart the installation procedure for the UNIX shell, enter restart.

The distribution media (CD-ROM or RIS) contains file systems that are laid out just as the software would be installed on the system and contains directly accessible root, /usr, and /var areas. This format makes almost every Digital UNIX command and utility available in the UNIX shell even if your operating system is not yet fully functional. In effect, the mounted distribution media is a complete Digital UNIX file system.

The UNIX shell provides a way for you to recover from serious problems such as root file system corruption and enables you to perform general file system and disk maintenance tasks during the installation. Digital recommends that only experienced users choose the UNIX shell option.

Refer to Chapter 7 for more information about the UNIX shell.

1.7    Summary of the Installation Procedure

Table 1-7 summarizes the procedure for the default and custom installations regardless of the interface (graphical or text-based). Review these steps to prepare yourself for the information you must enter during the actual installation procedure.

If you decided to perform an update installation, Chapter 2 contains all the information you need.

If the RIS administrator has set up your system for a cloned installation, make sure you perform the preinstallation tasks described in Section 1.4 and then boot your system from the RIS server as described in Chapter 4. Refer to Section 5.1.3 for the sequence of events during a cloned installation.

Table 1-7: Summary of the Full Installation Procedure

1.8    If Your System Has Factory Installed Software (FIS)

Your system may have been delivered to you with Factory Installed Software (FIS); that is, a version of Digital UNIX is already installed. Included in the box with your system is the Factory Installed Software Information Sheet that describes the software products that are preinstalled for you and how the system is configured.

Connect the hardware as shown in the hardware documentation, and turn on power to the processor and monitor. After some initial system initialization messages are displayed, you are prompted to enter information such as the system's host name, root password, geographic location and time zone, and the current date and time. The FIS Quick Reference Card is also included in the box with your system and describes how to respond to the prompts for this information. After the kernel build process is complete, refer to Chapter 6 for information about setting up your system for general use.

If the FIS setup halts unexpectedly and you see the root system prompt (#), make a note of any error messages that appear on the screen. Then, press Ctrl/d to restart the configuration phase. Usually the installation continues, but you will need to correct the error when setup is complete. Refer to the appropriate Digital UNIX document or hardware document to identify and correct the error.

If the error prevents the configuration from proceeding, it may be necessary to reinstall Digital UNIX. To do this, boot your processor as shown in Chapter 4 and refer to Section 1.5 to decide whether you need to do a default or custom installation. You can also consult the RIS system administrator to determine if your system is a suitable candidate for a cloned installation. If you choose the custom installation, be aware that the system disk may already have a customized disk partition table. The customization is usually done at the factory to create disk partitions that are large enough to hold all the software originally installed on the disk.

During the text-based custom installation, you are asked whether you want to preserve the customized partitions or use the default partition table. This option is described in Section 5.8.5. If you choose not to preserve the customized partitions, you may not be able to reload all the software that was originally installed.

A FIS system is generally installed with all base operating system software subsets (those that are prefixed with OSF) and some associated products. If you do not need to reinstall all the original software subsets and want to install mandatory software subsets only, perform a default installation. If you want to install mandatory and optional software, perform a custom installation. Use the setld command if you want to install or remove software subsets after an installation.

The default and custom installation procedures are described in Chapter 5.

1.9    Installing Worldwide Language Support Software

Digital UNIX is an internationalized operating system. The worldwide language support software subsets provide support for various native languages and countries. Installing the worldwide language support software subsets enables software developers to develop internationalized software that can be used in different countries.

If you want to install Digital UNIX Version 4.0 worldwide language support software subsets, your system must already be installed with the Digital UNIX Version 4.0 base operating system. Then, follow the worldwide installation instructions in Chapter 9.

The worldwide language support software subsets are located on the CD-ROM labeled Digital UNIX V4.0 Associated Products Volume 1.

If you want to perform an update installation of the worldwide language subsets from Digital UNIX Version 3.2C, 3.2D-1, or 3.2D-2 to Digital UNIX Version 4.0, follow the worldwide update installation instructions in Chapter 10.

Descriptions of the worldwide language support software subsets are located in Appendix E.