test

Solaris 9 Maintenance Update 4 Installation Guide

Chapter 2 Installing the Solaris 9 Maintenance Update 4

This chapter describes how to install the Solaris 9 MU4 software. If you are installing the Solaris 9 MU4 software as part of a custom JumpStartTM installation, refer to the Solaris 9 Installation Guide.

Time Considerations

The amount of time it takes to install the Solaris 9 MU4 varies, depending on the following factors:

Note –

If you install the MU4 with the -d option disabled, the installation proceeds more quickly. However, if you use this option when you install the MU, you cannot back out any of the patches MU4 delivers.

Installation Requirements

The MU4 can only be installed on a system that is running the Solaris 9 operating environment.

Space requirements for each file system vary, depending on the following criteria:

The install_mu script performs a space analysis. The script reports the space that is needed for each file system, including backout space if applicable. The space calculations are completed in several minutes.

The install_mu script does not proceed if the script determines that space is lacking in one or more file systems. The patch installation space that is needed is calculated with some precision. However, the backout data space need is estimated. The reported need might be higher than the actual need.

Run the install_mu script with the -f option if you meet both of the following conditions:

Installing the Solaris 9 MU4

Solaris 9 MU4 software can only be installed if the system that is running install_mu is already running the Solaris 9 operating environment.

Note –

Relocatable root and service areas are not supported in the Solaris 9 MU4.

Ideally, reboot the system in single-user mode before installing MU4, because MU4 applies patches to system libraries. Avoid introducing instability to individual systems in a multiuser system. Ensure that no processes have mapped to an unpatched version of a library. Otherwise, those processes might later attempt to map to different sections of the old library.

In single-user mode, network services are not available. You must first copy the MU4 image from the network to your local system before booting the system in single-user mode.

You need to install MU4 by using NFS in multiuser mode, if you meet one of the following conditions:

In this case, you should have the system in as quiet a state as possible. No users should be logged in or running any jobs.

When in single-user mode or multiuser mode, you must reboot your system after MU4 is installed. Do not use the exit command. If the exit command is used, the system is brought to init 3, and no user can log in until the system is rebooted. If the root user has logged out, and no other root users remain logged in, the system must be rebooted. See Chapter 4, ”Known Problems”, for more details.

Note –

Ensure that you have backed up your operating system before proceeding.

To install the Solaris 9 MU4 software, perform the following steps:

  1. Ensure that no important user or important system processes are running.

    Note –

    You must kill the powerd process if that process is running.

  2. Exit the current session.

    The CDE login screen is displayed.

  3. Click the Options button and select Command Line Login.

    The system prompts you to log in.

  4. Type your login name as root and type the root password:


    login: root
password: root password

  5. Reboot the system in single-user mode. From the root shell prompt, type the following command:


    # reboot -- -s

  6. Type the root password.

    Check that the system displays the following message and is now in system maintenance mode:


    Entering System Maintenance Mode
 
Sun Microsystems Inc. SunOS 5.9 Generic May 2002
#

  7. Run the install_mu script. From a local copy of the MU4 image, type the following commands:


    # cd local–directory
# ./install_mu options

    The following table lists options you can use from the command line.

    Table 2–1 Command-Line Options for install_mu Script

    Option 

    Description 

    -d

    Specifies that patches are not backed up. Use of this argument decreases the time to install the software, but it also prevents you from backing out individual patches. Cannot be specified with -B option.

    -p patchdir

    Specifies directory that includes all the patches. 

    -q

    Disables the display of dots that indicate install_mu activity.

    -B backoutdir

    Specifies that the backout data is saved in the indicated directory. Cannot be specified with the -d option.

    -f

    Forces installation of patch set without checking for sufficient disk space. Use of this option is quicker. However, use this option only if you know that you have enough space.  

  8. When the installation is complete, check that the following message is displayed:


    install_mu completed at date–time.

  9. Reboot the system by typing the following command:


    # sync ; reboot

    You are then prompted for a login.

    Note –

    To prevent the library conflict problem, you must reboot your system after installing MU4.

  10. Type your login name and password:


    login: login
password: password

Identifying the Version of Your Solaris 9 Maintenance Update

To identify the version of your Solaris 9 MU software, type the following command:


# cat /etc/release

To identify the patches the MU software applied to your system, type the following command:


# showrev -p

Note –

If you compare the showrev -p output from applying the Solaris 9 MU4 software to the showrev -p output from installing the Solaris 9 8/03 operating environment, you will note that the following patches are not applied in the MU4 installation: