2    Performing an Update Installation

All the information you need to perform an update installation is included in this chapter. This chapter includes the following information:

Note

If you want to update a system that has Worldwide Language Support (WLS) installed, use the update procedures shown in Chapter 12. The wwinstallupdate program deletes worldwide support subsets, invokes installupdate to update the base operating system software subsets, and then updates worldwide support subsets and merges the saved system files.

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

Table 2-1:  Summary of User Actions

After reading this chapter, you will ...
Perform prerequisite tasks before starting the update.
Decide whether to use CD-ROM or the network as the distribution media.
Perform prerequisite tasks based on the media you choose.
Start the update installation from CD-ROM or RIS.
Respond to prompts during the early phase of the update.
Use the Update Administration Utility to perform postinstallation tasks.
Run the catman -w command to update the whatis reference page database.

2.1    Quick Start for Experienced Users

If you have performed an update installation before, you probably do not have to read the detailed information in this chapter. The Update Installation Quick Reference Card is intended for experienced users, and you may want to consider using it as a guide when performing the update installation.

Table 2-2 provides the steps to get you started quickly.

Table 2-2:  Steps for Experienced Users

If you have experience performingupdate installations... FollowInstructions In:
Perform prerequisite tasks. Section 2.5
Start the update installation from CD-ROM. Section 2.6
Start the update installation from RIS. Section 2.7
Manually merge files if necessary. Section 2.11
Perform file administration tasks using the Update Administration Utility. Section 2.16

2.2    What Is an Update Installation?

An update installation updates your operating system from the previous version to the current version. You cannot update your system directly to the current version of the operating system from an earlier version; you must perform successive updates to reach the current version of the operating system.

Table 2-3 provides the steps necessary to perform successive updates.

Table 2-3:  Successive Update Paths

If you are currently using... Update the operating system to..
Version 3.2, 3.2A, or 3.2B Version 3.2C by using the installupdate command
Version 3.2C, 3.2D-1, or 3.2D-2 Version 4.0 by using the installupdate command
Version 3.2E-1, 3.2E-2, or 3.2F Version 3.2G by using setld -l
Version 3.2G Version 4.0A by using the installupdate command
Version 4.0 or 4.0A Version 4.0B by using the installupdate command
Version 4.0B or 4.0C Version 4.0D or 4.0E by using the installupdate command
Version 4.0D or 4.0E Version 4.0F by using the installupdate command

If you require additional versions of the operating system, contact your customer service representative.

An update installation preserves disk partitions, file systems, file customizations, your print and network configuration, user accounts, user files, and any other system setup you may have done on a system that is running the previous version of the operating system. Preserving this data is an advantage over a full installation, because a full installation creates new 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.

Base software subsets that are already installed on your system are updated to the current version. In addition, any mandatory base software subsets that were introduced in this version are installed automatically. Operating system base software subset names start with the prefix OSF and can be viewed by using the following command line: 

# setld -i | grep ^OSF
 

You cannot install additional optional software subsets during an update installation. Additional optional software subsets can be installed by using the setld command when the update installation is complete. Refer to Chapter 10 for more information about using the setld command.

Layered products are not updated by the update installation process. To update layered products, it may be necessary to delete the existing version and reinstall the new version after the base update installation process completes. Refer to the installation instructions provided with the layered product.

2.2.1    Completion Time for an Update Installation

Update installations from RIS complete in 90 to 120 minutes. Update installations from CD-ROM complete in 90 to 150 minutes. Actual time depends on your processor type, the number of software subsets to be updated, the type of media used to perform the update (CD-ROM or RIS), the speed of your CD-ROM drive if you are using CD-ROM, and network traffic if you are using RIS.

2.2.2    How Existing Files Are Affected During an Update Installation

This section describes the files that are affected by the update installation.

The update installation does not delete any user files (that is, files that have been created by system users that were not shipped as part of the operating system). The files that the update installation affects are the following:

2.3    Source of the Update Installation

There are two distribution methods from which to invoke an update installation:

The update installation is performed from single-user mode. You must be superuser or the user root to bring a system down to single-user mode. How you bring the system down to single-user mode depends on the following:

The procedure to start the update from the command line depends on whether you are using CD-ROM or RIS as the source of the update. Section 2.6 describes how to start the update from CD-ROM, and Section 2.7 describes how to start the update from RIS.

Caution

Do not use the setld -l command to update from Version 4.0D or 4.0E to the current version of the operating system. The only method to update your system other than performing a full installation is to use the /sbin/installupdate program that is described in this chapter.

2.4    Summary of the Update Installation Procedure

The following list summarizes the steps in an update installation:

  1. Perform the prerequisite tasks that must be completed regardless of the distribution media you are using. These tasks include backing up your system, deleting layered products that will halt the update process, updating your system firmware, and checking disk space. These tasks are described in Section 2.5.

  2. Decide whether you are updating from the CD-ROM or RIS distribution media and perform prerequisite tasks depending upon what distribution media you choose. Refer to Section 2.6.1 for CD-ROM prerequisite tasks. Refer to Section 2.7.1 for RIS prerequisite tasks.

  3. Start the update installation.

  4. Respond to prompts during the initial phase of the update.

  5. Perform postinstallation tasks:

2.5    Preparing for an Update Installation

Whether you are performing the update installation from CD-ROM or a RIS server, you must perform the following tasks before you begin:

  1. If you are not using AdvFS on your system, proceed to the next step.

    If you are using AdvFS on your system, perform the following procedure to protect your data on AdvFS file domains:

    1. Log in as root or use the su command to gain super-user privileges.

    2. Use the shutdown command to put your system into single-user mode. Refer to the shutdown(8) reference page.

    3. Use the umount -A command to unmount all local file systems. Refer to the mount(8) reference page.

    4. Run the verify utility on each local file system. If you find any problems, correct them before continuing. Refer to the verify(8) reference page.

    5. Use the mount command to mount all of the verified local file systems. Refer to the mount(8) reference page.

    6. Use the quotacheck command to fix the quotas on the mounted local file systems. If you have problems running the quotacheck command, you may have to edit your /etc/fstab file and try again.

  2. If you previously performed an update installation on your system, you should have used the Update Administration Utility to remove unnecessary files before attempting the next update installation. When you invoke the Update Administration Utility to view files, the message deleted from system indicates that you had used the utility to delete files after the last update installation. If you have not removed any files, please do so now. The Update Administration Utility lets you remove .PreMRG, .PreUPD, and obsolete files that may conflict with the newly loaded software subsets. Removing these files also frees up disk space. Refer to Section 2.16 for more information about using the Update Administration Utility.

  3. Back up your current operating system.

    You should back up your operating system before beginning an update installation. If there are any interruptions when the update process is loading software subsets, it is unlikely that the update will complete successfully. Should this happen, you must restore the original version of the operating system that was previously installed on your system before you can attempt another update. Refer to System Administration for information about backing up your current system.

  4. Delete layered products that block the update installation before starting the process..

    Some layered products must be deleted before the update installation can proceed. Section 2.8.3.1 shows an example of the messages you will see if these layered products are detected during the update process. The software subsets associated with the layered products in Table 2-4 halt the update installation and must be deleted before beginning the update:

    Table 2-4:  Update Install Blocking Products

    Product Description Subset Prefix
    ADP Subsets ADP
    DECsafe Available Server Environment (ASE) ASE
    Atom Advanced Developers Kit ATM
    Distributed Computing Environment/Distributed File System (DCE/DFS) DCE
    DECnet OSI DNA
    Event Manager (EVM) Subsets EVM
    Worldwide Language Support [Footnote 3] IOS
    Internet Protocol (IP) Version 6 Early Release Kit IP6
    Kubota Workstation Software KWS
    Multimedia Services [Footnote 4] MME
    Open 3D Subsets O3D
    Pathworks Subsets PWK
    System V Environment (SVE) Subsets SVE

    Use the setld command to delete the software subsets associated with these layered products. Section 2.8.3.1 describes how to delete layered products.

  5. Check disk space.

    If your file systems have less space available than the amount shown in the Software Subsets Information appendix to the Release Notes, consider using the setld command to delete unnecessary software subsets before you begin the update. You should also remove all unnecessary kernel files and core files that are consuming space. Refer to Chapter 10 for more information about using the setld command.

    Use the df command to check your current disk usage. Refer to the Software Subsets Information appendix to the Release Notes for information on the disk space requirements for the update installation.

  6. Update system firmware.

    To run this version of the operating system, your system might require a firmware update. Firmware updates are located on the Alpha Systems Firmware CD-ROM that is included with your operating system software distribution kit. Update your system's firmware before beginning the update installation. Section 1.4.6 provides the minimum firmware revision for each supported processor.

After you have completed all prerequisite tasks, proceed to Section 2.6 if you are using the operating system CD-ROM to perform the update. Proceed to Section 2.7 if you are using RIS to perform the update.

2.6    Running the Update Installation from CD-ROM

Read this section if you are performing an update installation from CD-ROM media.

2.6.1    Before You Start

If you are updating your system from CD-ROM, you need to know the system device name of the drive where you will load the CD-ROM.

If you do not know the system device name of your CD-ROM drive, log in as root or use the su command to gain root privileges, and enter the following command: 

# file /dev/rrz*c | grep RRD
/dev/rrz4c: character special (8/4098) SCSI #0 RRD44 disk #32 (SCSI ID #4)

In this example, the CD-ROM device is RRD44 on device /dev/rz4c. If you have more than one RRD device connected to your system, determine the device where you will mount the CD-ROM.

Note

You must have root privileges to get this information with the file command.

Standard device names begin with rz for the block special file and rrz for the raw (character) special file. The result of the file command displays the raw device name, but you must specify the block special file when mounting the CD-ROM device. In this example, the displayed device name is /dev/rrz4c, but you will use /dev/rz4c.

If any hardware product kit installed on your system will need to be updated to work with the new operating system version, you also need to know the console device name of the CD-ROM drive you will use to load the new version of the kit. To determine the console device name of your CD-ROM drive, shut down your system and enter the following command at the console prompt:

>>> show dev
 

Your output will be similar to the following:


dka0.0.0.1001.0        DKA0        RZ28D    0010
dka500.5.0.0.1001.0    DKA500      RRD46    0557
dva0.0.0.0.1           DVA0
ewa0.0.0.1000.0        EWA0        hw_ethernet_address
pka0.7.0.1001.0        PKA0        SCSI Bus ID 7 5.01
pkb0.7.0.1001.0        PKB0        SCSI Bus ID 7 5.01
 

CD-ROM drive types have an RRD prefix; in this example, the console device name of the RRD46-type CD-ROM drive is DKA500.

2.6.2    Starting the Update Installation from CD-ROM

Perform the following steps to start the update installation from CD-ROM:

Note

Before beginning the update installation, be aware that the process takes from 90 to 150 minutes to complete. Actual time depends on your processor type, the speed of your CD-ROM drive, and the number of software subsets to be updated.

  1. Verify that your system is backed up so that you can recover the previous version if necessary. The System Administration guide documents backup procedures (using the dump command).

  2. As superuser or root, boot to single-user mode or shut down your system.

    Once your system is in single-user mode, the screen looks similar to the following: 

    INIT: SINGLE-USER MODE
#

  3. Follow this step only if you installed and are using the Logical Storage Manager (LSM); otherwise, proceed to Step 4.

    Enter the following command to activate LSM before running bcheckrc (in Step 4): 

    # /sbin/lsmbstartup

  4. Mount the local file systems as follows: 

    
# /sbin/bcheckrc

    The bcheckrc command also runs fsck to check the file system. If fsck finds a problem with the root ( / ) partition, the system shuts down and reboots.

  5. Load the CD-ROM into the drive. Refer to Appendix B if you need additional information.

  6. Use one of the following methods to start the update installation from CD-ROM.

    Note

    The optional -i flag invokes an interactive kernel build where you can select kernel options from a menu and edit the configuration file to include any kernel customizations that you had in the previous kernel that your system may require.

Caution

Pressing Ctrl/c during the update installation causes installupdate to exit. However, if you press Ctrl/c while software subsets are loading, serious operating system corruption can occur that may render the operating system unusable. In that case, you may have to restore the backed-up version of the operating system before you can attempt another update.

Proceed to Section 2.8 to continue the update installation.

2.7    Running the Update Installation from a RIS Server

Read this section if you are performing an update installation from a RIS server.

2.7.1    Before You Start

Complete these steps before you start the update installation from a RIS server:

  1. Ask the RIS server administrator to ensure that your system is registered as a client of the RIS server and is able to access the RIS area that includes the current version of the operating system. Refer to Sharing Software on a Local Area Network for more information about RIS.

  2. The Internet name and address of the server may need to be in your system's /etc/hosts file in order for you to execute the showmount command. You can invoke the netconfig application to add the name and address of the server or edit the /etc/hosts file to include an entry for the server, similar to the following: 

    16.141.113.221 system9.dec.com system9

    The hosts entry in /etc/svc.conf must allow for local resolution of host (Internet) addresses, for example: hosts=local,yp. You can invoke the svcsetup command to modify hosts to local or edit the /etc/svc.conf file. Refer to Network Administration if you need more information about obtaining network status. Refer to Sharing Software on a Local Area Network if you need more information about RIS.

  3. Ensure that 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 ris_server_name with the name of your local RIS server: 

    # /sbin/ping -c2 ris_server_name

    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:

  4. Verify that your system is backed up so that you can recover the previous version of the operating system if necessary.

2.7.2    Starting the Update Installation from a RIS Server

Perform the following steps to start the update installation from a RIS server:

Note

Before beginning the update installation, be aware that the process takes from 90 to 150 minutes to complete. Actual time depends on your processor type, the speed of your CD-ROM drive, and the number of software subsets to be updated.

  1. Log in as root or use the su command to gain superuser privileges.

  2. Boot to single-user mode or shut down your system.

    When your system is in single-user mode, the screen looks similar to the following: 

    INIT: SINGLE-USER MODE
#

  3. Follow this step only if you installed and are using the Logical Storage Manager (LSM); otherwise proceed to the next step.

    Enter the following command to activate LSM before running bcheckrc (in Step 3): 

    # /sbin/lsmbstartup

  4. Mount the local file systems as follows: 

    
# /sbin/bcheckrc

    The bcheckrc command also runs fsck to check the file system. If fsck finds a problem with the root ( / ) partition, the system shuts down and reboots to multiuser mode.

  5. Enter the following command to delete the table of Internet addresses to ensure that the routed and gated daemons do not start up during the update installation: 

    
# route flush

    Successful completion of the route flush command looks similar to the following: 

    default      16.70.223.135   done
16.70.143    16.70.223.198   done

  6. Enter the /sbin/installupdate command with the following syntax:

    /sbin/installupdate [-i] ris_server_name:

    The optional -i flag invokes an interactive kernel build where you can select kernel options from a menu and edit the configuration file to include any kernel customizations that you had in the previous kernel that your system may require.

    For example, to run /sbin/installupdate from a RIS server named system9 with an interactive kernel build, enter a command similar to the following: 

    # /sbin/installupdate -i system9:

    The RIS server name must be followed by a colon ( : ).

    Caution

    Pressing Ctrl/c during the analysis phase of the update installation causes installupdate to exit. However, if you press Ctrl/c while software subsets are loading, serious operating system corruption can occur that may render the operating system unusable. In that case, you may have to restore the backed-up version of the operating system before you can attempt another update.

Proceed to Section 2.8 to continue the update installation.

2.8    What Happens During the Update Installation Process

This section describes the information and prompts that are displayed during the update installation process.

The number of software subsets installed on your system and the type of installation media used affects the time required for an update. You are required to enter information during the early phases of the update. You do not need to monitor the update under most circumstances. However, if an error occurs, messages notify you and offer options for proceeding.

The phases of the update installation include the following:

Note

If you are updating from an earlier version of the operating system and you are using the Dynamic Driver Recognition (DDR) database, it is converted to a new format that includes formerly unrecognized SCSI device types and IDE/ATAPI entries. However, the running kernel is still based on the older DDR database format and the following messages are reported to the system console:


DDR: Invalid Database Header
DDR: Invalid Database Header

You can ignore these messages. At the end of the update installation, the updated ddr.mod binary is included in the new kernel that recognizes the converted DDR database.

The following sections describe the information displayed on your screen during each phase of the update.

2.8.1    Checking for Installed Hardware Product Kits

If the update installation process finds an installed hardware product kit, it is checked for compatibility with the new version of the operating system. One or more of the following conditions may apply:

2.8.2    Verifying the System State

The first message displayed on your screen confirms the new version of the operating system, and the version that you are updating from. This message also reminds you that your system should be backed up so that you can recover the current version of the system if an interrupt should occur. 

The DIGITAL UNIX Version 4.0F (Rev. nnn) Update Installation will
update the following DIGITAL UNIX products:
 
        DIGITAL UNIX V4.0D
        DIGITAL UNIX V4.0E
 
Compaq Computer Corporation recommends that you perform complete
system software backups before proceeding.

At this point, the update procedure also checks for certain layered products that may be incompatible with update installations. If these products are found on your system, warning messages are displayed as described in Section 2.8.3. If the layered product messages are not displayed, and you are satisfied with the state of your system backup, you can proceed with the update. A prompt is displayed as follows: 

Do you want to continue the update installation? (y/n) [n]:

Enter y to proceed with the installation or n if you want to exit and back up your system.

2.8.3    Checking for Layered Products

This section applies only if the update installation detects layered products that may not be compatible with this version of the operating system.

If no layered products are found, proceed to Section 2.8.4 to continue the update installation.

In this version of the operating system, installupdate checks if certain layered products are installed on your system. Layered products are products that are installed on top of the operating system. If detected, these layered products may be affected by the update as follows:

2.8.3.1    Layered Products That Halt the Update Installation

If applications or layered products installed on your system prevent installupdate from continuing, a message similar to the following is displayed: 

-----------------------------------------------------------------
This system cannot be updated with the following layered products
installed on it.  Please remove these products from your system
before attempting an update installation:
 
    DECnet/OSI
    DEC Open3D
    DECsafe Available Server Environment
    Kubota Workstation Software
    Multimedia Services
    Distributed Computing Environment
    System V Environment
    Worldwide Language Support
 
------------------------------------------------------------------
Press <RETURN> to review message again.

If this message appears, the update installation cannot proceed and you must exit at the following prompt: 

Enter 'stop' and press <Return> to stop:

When you enter a character and press Return, your system is returned to its original state, that is, the state your system was in before the update procedure.

Follow these steps to delete the layered product that is preventing the update installation from continuing:

  1. Use the setld -i command to determine the correct software subset names to delete.

    In the following example, assume that DECnet/OSI prevented your update installation from continuing. Refer to Table 2-4 to determine that the subset prefix associated with DECnet/OSI is DNA, and use the following command to determine the software subset names associated with DECnet/OSI: 

    
# setld -i | grep DNA | grep installed
DNABASE440      installed      DECnet/OSI Base Components
                                 (DECnet/OSI Standard Run-time
                                 Environment)
DNADLI440       installed      DECnet/OSI Datalink Components
                                 (DECnet/OSI Standard Run-time
                                  Environment)
DNAMOP440       installed      DECnet/OSI MOP Utilities
                                  (Optional DECnet/OSI
                                   Components)
DNANETMAN440    installed      DECnet/OSI Network Management
                                 (DECnet/OSI Standard Run-time
                                  Environment)

    The output shows that DNABASE440, DNADLI440, DNAMOP440, and DNANETMAN440 are the installed DECnet/OSI software subsets that must be deleted.

  2. Use the setld -d command to delete the software subsets: 

    # setld -d DNABASE440 DNADLI440 DNAMOP440 DNANETMAN440

  3. After software subset deletion is complete, restart the update installation:

When the update installation is complete, use the setld command to reinstall the version of the layered product that is compatible with this version of the operating system.

2.8.3.2    Layered Products That Do Not Halt the Update Installation

If any layered products currently installed on your system let installupdate continue but may require reinstallation, a message similar to the following is displayed: 

----------------------------------------------------------------
The following layered products may require re-installation after
the update installation has completed:
 
	    Product A
 
        
.
.
.
Product Z
----------------------------------------------------------------
Press <RETURN> to review message again.

You have the option to exit from the installation procedure at this point and the following prompt is displayed: 

Do you want to continue the update installation? (y/n) [n]:

Enter y to proceed with the update installation or n if you want to exit the update installation and remove the layered products before restarting the update.

If you decide to proceed without removing these layered products, test the layered product when the update is finished. You should reinstall any layered products that are critical to the use of the updated operating system. Proceed to Section 2.8.4 to continue the update installation.

2.8.4    Checking the System Status

The next step in the update involves checking the system status and collecting data that is used in the update. This step takes up to 10 minutes, and you are not required to enter any data.

A Working... message displays approximately once every two minutes while system status is checked. These messages are similar to the following: 

******   Checking current state of system
 
Depending on the system configuration, this may take
up to 10 minutes...
        Working....Fri Dec 17 12:10:27 EST 1999
        Working....Fri Dec 17 12:11:52 EST 1999
        Working....Fri Dec 17 12:13:59 EST 1999

During this phase of the update, the update procedure does the following:

If no problems are detected during the checking phase, you do not need to enter any more information beyond this point. If no conflicts are displayed, proceed to Section 2.8.8 to continue the update installation process.

2.8.5    Checking for File Type Conflicts

This section applies only if file type conflicts are found by the update installation procedure.

System file types can be files, directories, symbolic links, block devices, or pipes. The update installation procedure expects to find system file types currently installed as they were shipped with the base operating system. The status of each file type is verified during the system status check. For example, if a file is shipped as type symbolic link in an earlier version of the operating system and you later customize it to a type directory, when the same file ships as type symbolic link in this version of the operating system, the update installation detects the difference and exits.

When file system types are modified as part of a system customization, the update installation cannot proceed. This is intended to preserve the integrity of the software product about to be installed.

Messages display when file type conflicts are found. In the following sample message, /usr/tmp was shipped as a symbolic link and was changed to a directory: 

The following directories on this system conflict with assigned file
types originally shipped in the DIGITAL UNIX operating system.  This
can be caused, for example, if a symbolic link is replaced with a
real directory.
 
These conflicts must be resolved before an update installation can be
performed on this system.   Additional file status information can be
found in subset inventory files located in the /usr/.smdb. directory.
 
For later review, this message is also logged in
 
        /var/adm/smlogs/update.log
 
The update procedure will exit and return the system to its original state
 
        ./usr/tmp should be Symbolic Link to ../var/tmp
 
 

You can review the list of file conflicts or exit as follows: 

Press <RETURN> to review message again.
Enter any character and press <RETURN> to exit:

When you exit from the update procedure, the following message is displayed: 

Returning system to Pre-Update state...done.
Exiting Update Installation.

You must resolve any conflicts shown in the message before you can restart the update installation. If you do not resolve the conflicts, you cannot perform an update installation.

2.8.6    Checking File Space Requirements

The update installation procedure performs file system size checks to make sure that the list of new software subsets fits on your system. In the preparation stage before the update, you should have removed all unwanted core files, crash dumps, and extra kernels that may be consuming space.

This section describes what happens when your system has sufficient disk space and what happens when your system has insufficient disk space. It also provides guidelines on how to recover additional free disk space.

2.8.6.1    System Has Sufficient Disk Space

If the update installation process determines that there is adequate space for all new software subsets, no user interaction is required, and the process continues by loading the software subsets as shown in Section 2.8.8.

2.8.6.2    System Has Insufficient Disk Space

If the update installation determines that there is inadequate space for the loading of new software subsets, it attempts to recover space from saved unprotected customized files (such as files with the .PreUPD extension). One of the following three instances may occur:

2.8.6.3    Deleting Individual System Files Does Not Free Space for the Update

Deleting individual files that are part of installed base or layered product subsets will not produce additional free space because the update installation takes into account that these old files will be replaced by new versions. The disk space calculation determines how much additional space is needed to replace an old version of a file with its new version.

If the old version of a file is removed without removing the entire subset in which it resides, the update installation Administration Utility lets you save the unprotected customized files to another file system or delete the files manually. However, you still will put the new version on the system. In this situation, the full size of the new file will be allocated instead of the difference between the size of the original and new versions.

For example, if /genvmunix was 7MB and a new version of /genvmunix was 8MB, update would need to reserve 1MB of free space for the new version. If /genvmunix was deleted before the update, the disk space calculation would then reserve the full 8MB for the new file. So, although, 7MB was freed before the update, 7MB more would be reserved during the update, which would result in no difference in the amount of additional space needed to continue the update.

2.8.6.4    How to Obtain Additional Space

To obtain additional space necessary to perform the update installation, follow these guidelines:

2.8.7    Detecting Unprotected Customized File

This section applies only if unprotected customized files are detected during the update installation.

If installupdate detects any unprotected customized system files as described in Section 2.2.2, an attempt is made to save them to a .PreUPD extension, for example, custom_file.PreUPD, so that you can decide what to do with them after the update is complete.

If for any reason unprotected customized files cannot be saved, the Update Administration Utility is invoked automatically and lets you view these files and save them to backup media. The file name of each unprotected customized file is also logged in the /var/adm/smlogs/upd_custom_files file as a reminder of the files that require recustomization.

Files that are successfully saved to the .PreUPD extension are listed as such in the file /var/adm/smlogs/upd_custom_files.

The following message is displayed if customized files are found and successfully saved: 

     Unprotected customized system files have been found on
     this system and have been saved by renaming them with 
     'PreUPD' file name extension.  A listing of the files 
     and their associated subset, can be found in
     /var/adm/smlogs/upd_custom_files.
 
     After the update installation has completed, you can use 
     the Update  Administration  Utility  (/usr/sbin/updadmin)
     to perform system administration tasks on these files.
 

The following message from the Update Administration Utility is displayed if customized files are found but could not be saved: 

**** Unprotected Customized System File Administration ****
 
There are unprotected  customized  versions  of  DIGITAL UNIX
system files currently installed  on  your  system  that are in
danger of being overwritten by new DIGITAL UNIX
Version ver_num(Rev. nnn) versions of the files.
 
These files are  typically  customized  by users for projects
they may be working on, or by layered  product software
implementation.
 
If you haven't already backed up your system,  save these files
to back up media at this time.  You can restore these files back
onto your system after the update installation has completed.
 
     Unprotected Customized System File Admin Menu
     ---------------------------------------------
     s) Save files
     d) Delete files
     v) View list of files
     x) Return to installation
 
     Enter your choice:

In the previous example, the Update Administration Utility is invoked automatically, and the menu shows the available options. The Update Administration Utility is described in Section 2.16. If you choose to continue with the update, the following message is displayed: 

     A listing of unprotected customized system files
     found by the Update Installation has been logged
     in /var/adm/smlogs/upd_custom_files.
 
     After the update installation has completed, you can use 
     the Update  Administration  Utility  (/usr/sbin/updadmin)
     to perform system administration tasks on these files.

2.8.8    Loading Software Subsets

Next, installupdate loads the operating system software subsets that match the software subsets already loaded on your system. Additionally, all new mandatory software subsets that were introduced in this version of the operating system are loaded automatically. Optional software subsets are loaded only if they were loaded previously. If you want to install additional optional software subsets provided in this version of the operating system, you must load these by using the setld command when installupdate is complete.

Caution

If you press Ctrl/c while software subsets are loading, serious operating system corruption can render the operating system unusable. You may have to restore the backed-up version of the operating system before you can attempt another update.

While software subsets are being loaded, a series of messages similar to the following is displayed: 

******   Updating system to DIGITAL UNIX Ver_num (Rev.nnn)
 
43 subset(s) will be installed.
 
Loading 1 of 43 subset(s)....
 
Base System
   Copying from system9 (inet)
        Working....Fri Dec 17 15:21:01 EST 1999
   Verifying
 
Loading 2 of 43 subset(s)....
 
Base System - Hardware Support
   Copying from system9 (inet)
        Working....Fri Dec 17 15:23:28 EST 1999
   Verifying
 
Loading 3 of 43 subset(s)....
 
Compiler Back End
   Copying from system9 (inet)
        Working....Fri Dec 17 15:24:06 EST 1999
   Verifying
 
   
.
.
.
Loading 33 of 43 subset(s)....
 
Graphical Base System Management Utilities
   Copying from system9 (inet)
   Verifying
 
Loading 34 of 43 subset(s)....
 
Graphical System Administration Utilities
   Copying from system9 (inet)
   Verifying
 
Loading 35 of 43 subset(s)....
 
Graphical Print Configuration Application
   Copying from system9 (inet)
   Verifying
 
   
.
.
.
Loading 42 of 43 subset(s)....
 
Motif 1.1
   Copying from system9 (inet)
   Verifying
 
Loading 43 of 43 subset(s)....
 
Ref Pages: Admin/User
   Copying from system9 (inet)
        Working....Fri Dec 17 15:49:57 EST 1999
   Verifying
 
43 of 43 subset(s) installed successfully.

Individual software subsets can fail to load if a network interrupt, hardware problem, or file verification error occurs during the load process:

2.8.9    Recovering from Subset Load Failures

If the update installation fails before software subsets are loaded, you can usually recover. If necessary, you can bring your system back to multiuser mode by issuing the following command: 

# init 3

Error messages describe the type of error that occurred. Fix the errors reported by the messages and restart the update installation process. Refer to Section 2.6 if you are running installupdate from a CD-ROM, or Section 2.7 if you are running installupdate from a RIS server.

If the update installation fails during the loading of mandatory software subsets, you must restore your operating system back to the previous version that was installed on your system and reattempt the update installation after the failure is corrected.

Note

You may see the following message when installing subsets from a RIS server:


Broken Pipe

You can ignore this message.

2.9    Merging Software Subsets

When all software subsets are successfully loaded and verified, the protected customized system files are automatically merged with any customized files found on your system. Refer to Section 2.2.2 for a description of the protected files. A series of merge messages similar to the following may be displayed: 

*** Merging new file ./.new..DXsession into
            existing ./.proto..DXsession
 
 
Merge completed successfully.
 
*** Merging new file ./etc/.new..passwd into
            existing ./etc/.proto..passwd
 
            adding wnn entry
 
Merge completed successfully.
 
*** Merging new file ./etc/.new..rc.config into
            existing ./etc/.proto..rc.config
 
            Adding DHCP hooks
 
Merge completed successfully.
 

.
.
.
*** Merging new file
            ./usr/var/adm/sendmail/.new..sendmail.cf into
            existing
            ./usr/var/adm/sendmail/.proto..sendmail.cf
 
            adding local.users to sendmail.cf
            adding Mlocal "F=u" flag in sendmail.cf
            correcting Mlocal "F=r" flag in sendmail.cf
 
Merge completed successfully.
 
*** Merging new file
            ./usr/share/lib/kernel_options/.new..kernel_options .db into
            existing
            ./usr/share/lib/kernel_options/.proto..kernel_options.db
 
            modifying Asynchronous Transfer Mode option
            deleting Local Area Transport option
            adding Point-to-Point (PPP)
            adding ACL Subsystem
            adding NTP_TIME
 
Merge completed successfully.
 

When all merges are complete, the following message is displayed: 

Update Installation complete with loading of subsets.
Rebooting system with DIGITAL UNIX Ver_num (Rev. nnn)
generic kernel for configuration phase...
 
Exiting Update Installation...
 

A log file, /var/adm/smlogs/update.log, stores the results of software subset loading and merging for your reference.

If the update installation did not detect a hardware product kit in the analysis phase described in Section 2.8.1, the system reboots with a generic kernel and proceeds to configure software subsets as described in Section 2.11.

2.10    Bootlinking Supplemental Hardware Support

If the update installation detected a hardware product kit in the analysis phase described in Section 2.8.1, the system bootlinks the hardware support kernel modules.

  1. The boot utility issues the following prompt:

    Enter Device Name:

    Enter the console device name for your CD-ROM drive, such as DKA500, and press [Return].

  2. The boot utility issues the following prompt:

    Enter Kit Name:

    Enter the name of the hardware product kit that you want to install and press [Return]. This is the information that you saved in Step 4 of Section 2.8.1.

  3. The boot utility issues the following prompt:

    Insert media for kit 'device:hw_kit_name', press Return when ready:

    In this prompt, device is the device name that you entered in Step 1, and hw_kit_name is the hardware product kit name that you entered in Step 2.

    Load the CD-ROM into the drive and press [Return]. The boot utility reads the selected hardware product kit information into memory.

  4. The boot utility reissues the Enter Kit Name: prompt.

  5. The boot utility reissues the Enter Device Name: prompt.

  6. The boot utility and issues the following prompt:


    Insert boot media, hit <return> when ready:

    Since you are adding hardware support to a running system and the system disk is your boot media, just press [Return]. The generic kernel modules are read so that the bootlink process can build the kernel in memory in the next step.

  7. The boot utility links the kernel objects, and issues the following prompt:

    Insert media for kit 'dev_name:hw_kit_name', press Return when ready:

    In this prompt, dev_name is the device name that you entered in Step 6 and hw_kit_name is the hardware product kit name that you entered in Step 7.

    Put the CD-ROM into the drive and press [Return]. The hardware product kit kernel modules are read and the bootlink process builds the kernel in memory.

  8. The boot utility issues the following prompt:


    Insert boot media, press Return when ready:

    Since the boot media is still your installed system disk, just press [Return].

2.11    Configuring Software Subsets

If your system boots to multiuser mode, operating system software subset configuration starts automatically. If your system reboots to single-user mode, initialize multiuser mode with the following command: 

# init 3

Configuration refers to the process of tailoring the software subsets, setting the host name, root password, date and time, and time zone, system tuning, and building a kernel that is required to have your hardware operate correctly with the new operating system. The software configuration display is similar to the following: 

*** SYSTEM CONFIGURATION ***
 
Configuring "Base System " (OSFBASE440)
 
   *** Merging new file ./.new..DXsession into
               existing ./DXsession
 
           Merge completed successfully.
 
   *** Merging new file ./etc/.new..passwd into
               existing ./etc/passwd
 
           adding wnn entry
 
           Merge completed successfully.
 
   *** Merging new file ./etc/.new..rc.config into
               existing ./etc/rc.config
 
           Adding DHCP hooks
 
           Merge completed successfully.
 
                    
.
.
.
Configuring "Base System - Hardware Support " (OSFHWBASE440)
 
Configuring "Compiler Back End " (OSFCMPLRS440)
 
Configuring "Kernel Header and Common Files " (OSFBINCOM440)
 
        *** Merging new file
     ./usr/share/lib/kernel_options/.new..kernel_options.db into*
                        existing
     ./usr/share/lib/kernel_options/kernel_options.db
 
                modifying Asynchronous Transfer Mode option
                deleting Local Area Transport option
                adding Point-to-Point (PPP)
                adding ACL Subsystem
                adding NTP_TIME
 
                Merge completed successfully.
 
                    
.
.
.
Configuring "Hardware Kernel Objects " (OSFHWBINOBJECT440)
 
Configuring "Motif 1.1 " (OSFMOTIF11440)
 
Configuring "Ref Pages: Admin/User " (OSFMANOS440)

After the update installation completes, a record of the software subset configuration information is located in /var/adm/smlogs/it.log. Examine this log closely to check for merge failures because you will have to manually merge your customizations into these files. Manually merging means using the text editor of your choice to cut and paste customizations from the old version of a file into the new version. Refer to Section 2.15.3 for more information about manually merging files.

2.12    Loading and Configuring Hardware Support

If your system bootlinked supplemental hardware support as described in Section 2.10, the update installation loads and configures the hardware support kernel modules.

  1. If your hardware product kit CD-ROM is not in the drive or if additional kits are located on other media, you may see a prompt similar to the following: 

    The Update Installation has detected that the hardware support listed
below is loaded on your system and is not supported in the new
release of the Operating System (Ver_num). In order for the update to
complete successfully, you must provide the distribution media that
contains the Ver_num version of the hardware support listed below. The
update installation procedure will verify that the media you provide
contains the correct software.
 
	KIT_NAME_1
	KIT_NAME_2
 
     
    .
    .
    .
    Enter kit locations (e.g: /dev/rz3a or /mnt):

    If you press [Return] without entering a location for the listed kits, you see a prompt similar to the following: 

    If you choose to continue the update without providing the necessary
hardware support media, the following hardware will not function
after the update installation completes. Also, without the necessary
hardware support the update installation may not complete successfully and
may leave your system in an unusable state. Compaq recommends that
you do not continue with the update installation without the appropriate
hardware support.
 
	KIT_NAME_1
	KIT_NAME_2
 
     
    .
    .
    .
    Do you want to to continue? (y/n) [n]:

  2. Make sure that the hardware product kit CD-ROM is loaded into the CD-ROM drive.

  3. In response to the Enter kit locations prompt, enter the system device name or mount point of the CD-ROM drive where the hardware product kit is located and press [Return].

  4. You see a series of load progress messages, then a series of configuration progress messages.

  5. Until all required hardware kits are loaded and configured, the process returns to Step 1.

2.13    Building the Kernel

The kernel is built after software subset configuration is complete.

During the kernel build, the system configuration file /sys/conf/ SYSNAME is automatically saved to /sys/conf/ SYSNAME.bck, and a message similar to the following is displayed: 

Saving /sys/conf/LANSING as /sys/conf/LANSING.bck

In the previous example, lansing is the system's host name. If you customized this file, one of the postinstallation tasks is to edit the new version, include your customizations, and rebuild a tailored kernel with the customized configuration file.

The kernel build proceeds with the following messages: 

       The system will now automatically build a kernel
       and then reboot. This will take approximately 15
       minutes, depending on the processor type.
 
 
*** PERFORMING KERNEL BUILD ***
        Working....Fri Dec 17 13:25:43 EST 1999
        Working....Fri Dec 17 13:27:44 EST 1999

After the kernel builds successfully, you are prompted to log in to your system.

2.13.1    Manually Adding Special Configuration Options to the Kernel

The update installation provides a basic kernel configuration file that includes only the required options and pseudodevices needed to be compatible with the current installed version of the operating system. However, the update installation does not propagate any special configuration options such as those required for layered products.

If your system also has devices supplied by other manufacturers, you must add these options or devices to the kernel configuration file. Refer to System Administration for kernel build instructions.

Unless you invoked the update installation with the -i option or a hardware product kit was detected, you will not have the option to edit the configuration file before the kernel build and you must use the doconfig command to rebuild a customized kernel with any special options. Refer to Section 5.20 and the doconfig(8) reference page for more information.

2.13.2    Recovering from Kernel Build Failures

The tailored kernel build can fail at the end of your update installation because of an incompatibility of a kernel layered product with this version of the operating system.

In this case, the system will reboot with the generic kernel. The update installation log file located in /var/adm/smlogs/it.log contains the reasons for the kernel build failure. After examining the log, use the setld command to deinstall the layered product that caused the failure and then use the setld command to reinstall the most recent version of the layered product. You should then be able to build a new customized kernel with support for the layered product by using the doconfig command.

2.14    Logging In After the Update Completes

After the update installation is complete, log in to the system as the user root. You should log in as root so you immediately can perform the postinstallation tasks shown in Section 2.15, which can be done only by the user root.

What happens when you log in for the first time depends upon whether you have a graphics workstation or a text-based terminal without graphics capabilities:

Note

Device special file names may change as a result of the update installation. After successfully completing an update installation, it is possible that if you added tape devices to your system after the initial installation, the unit numbers and device special file names may be reordered as a result of the update process.

As an example, tape device tz13 is installed with device special file names *rmt0*. Then, tape device tz12 is installed and assigned device special file names *rmt1*. After an update installation, tape device tz12 is assigned device special file names *rmt0*, and tape device tz13 is assigned device special file names *rmt1*.

After you successfully log in, the update installation procedure is complete; your system is fully updated to this version of the operating system. Go to Section 2.15 for a description of the postinstallation tasks to perform. You can perform these postinstallation tasks only as the user root.

2.15    Postinstallation Tasks

This section describes tasks that must be completed after the update is complete.

2.15.1    Checking Installed Version String

To verify that you have installed all of the correct elements in this version of the operating system software kit, check the operating system revision level in the /etc/motd file. The correct version string is Tru64 UNIX V4.0F.

2.15.2    Reviewing Update Installation Log Files

Information about the update installation is stored in log files for you to review. Installation and configuration data is appended to any existing log files. Review the last entries in the following files to check the latest installation and configuration data:

If no obsolete, customized, or failed merge files are detected during the update installation, the relevant log files do not contain any data.

You should examine the log files when the update is complete to ensure that all files merged successfully.

2.15.3    Manually Merging Customizations

Some protected files may not be merged correctly during the update and all unprotected files are not merged automatically. Manual merging involves editing the new versions of system files with a text editor to apply your customizations. The following information is saved so that you can merge your customizations into the new versions.

When all manual merges are complete, your system is ready to use. At this time you can install additional optional software subsets provided on the operating system distribution media. Refer to Chapter 10 for information about installing optional software subsets.

2.16    Using the Update Administration Utility After the Update Installation

When you are satisfied that all merges are correct and your system is working as expected, use the Update Administration Utility to perform management tasks (such as saving, viewing, or deleting files) on the unprotected customized, obsolete, and PreMRG files. Unprotected customized files are saved to files with .PreUPD extensions.

Apart from managing system resources effectively, using this utility provides two important safeguards:

2.16.1    Invoking the Update Administration Utility

If your system has graphics capabilities, use one of the following methods to access the Update Administration Utility from the SysMan Configuration Checklist:

If your system does not have graphics capabilities, use one of the following methods to invoke the Update Administration Utility:

Regardless of the manner in which you invoked the utility, the Update Administration Utility Main menu is displayed as follows: 

The Update Administration Utility is used to perform administration
functions on a system that has been updated by /sbin/installupdate.
 
Please make a selection from the following menu.
 
        Update Administration Utility Main Menu
        ---------------------------------------
        c) Unprotected Customized File Administration
        o) Obsolete System File Administration
        p) PreMRG File Administration
        x) Exit this utility
 

To exit from the utility and return to the operating system prompt at any time, choose the exit option as follows: 

# Enter your choice: x

Choose the following options to perform file administration tasks (such as saving, viewing, or deleting files):

If you choose any of the three main menu options, a submenu is displayed. This submenu displays options to view, save, or delete the unprotected, obsolete, or PreMRG files.

The following examples show only Unprotected Customized File Administration. The administration process and the submenu options are exactly the same for Obsolete System File Administration and PreMRG File Administration.

To choose an option from any menu, enter the character displayed before each option and press the Return key. For example: 


# Enter your choice: c [Return]

2.16.2    File Administration Menu Options

If you choose any of the three Administration options from the main menu, the File Admin Menu is displayed as follows: 

	      Unprotected Customized System File Admin Menu
	      ---------------------------------------------
	      s) Save files
	      d) Delete files
	      v) View list of files
	      x) Return to previous menu

The type of the submenu depends on the option you chose from the Main menu. Enter x to return to the Main menu. The other options in this submenu are described in the following sections.

2.16.3    Save Files Option

This option lets you decide where to save the files that are found during the update installation. This option is useful for managing disk space.

If you choose this option, another menu is displayed as follows: 

	      Select a method of archiving your files:
        ----------------------------------------
	      d) Save files to directory on disk
	      i) Save files to tar image on disk
	      t) Save files to tape media device
 
	Enter your choice from the menu above, or
	press <RETURN> to go back to the previous menu:

The files are now saved. You can return to the File Admin Menu to choose either another option or exit to the Update Administration Utility Main menu.

2.16.4    Delete Files Option

This option lets you delete all the files (obsolete, PreMRG, or unprotected customized) that are found and created during the update installation. Use this option if you have either backed up the files to a storage device or if you no longer need them and you want to recover the disk space.

If you choose this option, the following prompt is displayed: 


Please confirm your intent to delete customized system files from the
system. (y/n) [n]: y

If you confirm the deletion, a message is displayed as follows: 

Removing customized files...
 
Finished deleting customized files.

When the deletion is complete, the File Admin Menu is displayed again.

2.16.5    View List of Files Option

This option is used to display a list of the customized files that are found during the update installation. It can be used to verify what files were found, before you decide whether you want to save or delete the files.

If you choose this option, the list of files is displayed screen by screen and you can press Return to display each screen. At the end of the list you can display the complete list again or return to the File Admin Menu. A sample of the output follows: 

./etc/zoneinfo/Australia/South.PreUPD
./sbin/named.PreUPD
./usr/sbin/screend.PreUPD
 
Enter 'r' to review files again, or press RETURN
to go back to the previous menu:

2.16.6    Messages and Archive Options

There are several messages and options that the Update Administration Utility displays only under certain conditions. These messages are explained as follows:

2.17    Updating the Reference Page Database

If the whatis database exists on your system, you should update the database by executing the catman -w command whenever you perform an update installation. The apropos and whatis commands access reference page entries in the whatis database.

An update installation does not delete entries from an existing whatis database. You must rebuild the database to synchronize it with reference page files that currently exist on the system. Rebuild the whatis database after you use the Update Administration Utility to remove reference pages that are flagged as obsolete after the update installation and after you are finished adding layered product reference pages.

For information about using the catman -w command to rebuild the whatis database, refer to the catman(8) reference page.

2.18    Postinstallation File Disposition

Several files are left over after the installation process completes. The following files are of particular interest: