test

Solaris 7 Maintenance Update 1 Release Notes (Intel Platform Edition)

Chapter 2 Installing the Solaris 7 Maintenance Update

This chapter describes how to install your Solaris 7 MU1 software on a standalone system or on a diskless client or SolsticeTM AutoClientTM from a server. If you want to install the Solaris 7 MU1 software as part of a customized JumpStartTM (automatic installation) process, refer to the Solaris Advanced Installation Guide.

Requirements

Space requirements per file system vary depending on:

The install_mu script performs a space analysis for you and reports the space needed per file system, including back out space if applicable. The space calculations take several minutes.

The install_mu script does not proceed if it determines that space is lacking in one or more file systems. Although the patch installation space needed is calculated fairly precisely, the back out data space need is estimated and the reported need may be higher than the actual need.

Note -

The MU may only be installed on a system running the Solaris 7 operating environment. In a client/server environment, the MU can only be applied to a client if both the client and server are running the Solaris 7 operating environment.

Installing Maintenance Update 1

Solaris 7 MU1 software can only be installed if both the system running install_mu and the target systems are already running Solaris 7.

It is best to reboot your system in single-user mode before installing MU1 because MU1 patches system libraries. On a multi-user system, your system will be unstable if any processes have mapped to an unpatched version of a library and later attempt to map to different sections of the old library.

In single-user mode, network services are not available. If the MU1 image is on the network rather than on a CD, you must copy the MU1 image from the network to your local system before booting your system in single-user mode.

If it is not possible to reboot the system in single-user mode or if you do not have enough disk space to make a local copy of the MU1 image, you will need to install MU1 using NFSTM in multi-user mode. In this case, you should have the system in as quiet a state as possible, without users logged or running jobs.

Note -

Be sure that you have backed up your system's operating system before proceeding.

To install the Solaris 7 MU1 software:

  1. Make sure that no important user or system processes are running.

  2. Exit the current session.

    The CDE login screen appears.

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

    The system prompts you to login.

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


    login: root
password: root password

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


    # reboot -- -s
    Note -

    Changing the run level from multi-user mode to single-user mode with the shutdown or init command might leave the vold process running. This may cause problems mounting the MU1 CD in single-user mode.

  6. Enter 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.7 Generic October 1998
#

    • If you are running install_mu from the CD, go to Step 7.

    • If you are running install_mu from a local copy of the MU1 image, go to Step 8.

  7. To mount the MU1 CD, place the CD in the drive and from the root shell prompt, type:


    # mount -o ro -F hsfs /dev/dsk/c0t6d0s0 /cdrom
    Note -

    In some cases, the CD-ROM drive may be on a different controller than c0 or a different target than t6, which would require a different path to the CD-ROM device. Check with your system administrator if you have questions about mounting the CD-ROM drive.

  8. Run install_mu.

    • From a local copy of the MU1 image, type:


      # cd local_directory
# ./install_mu any desired options

    • From the MU1 CD, type:


      # cd /cdrom
# ./install_mu any desired options

    The following options can be used on the command line.

    Table 2-1 Command Line Options for install_mu

    Option 

    Description 

    -u

    Unconditional install; does not verify that files to be updated were not changed since the initial installation. 

    -d

    Specifies that patches will not be backed up. Using this argument decreases the time it takes 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 back out data is saved in the indicated directory. Cannot be specified with the -d option.

    -f

    Force installation of patch set without checking for sufficient disk space. Using this option saves time, but you should only use it if you are certain that you have enough space. Cannot be specified with the -D option.

    -D

    Dry run mode; reports the amount of needed disk space without applying patches. Cannot be specified with -f option.

    -R rootdir

    Specifies an alternate root directory. Use to apply MU1 to clients whose package system information files are located in a directory tree starting in the specified rootdir. Cannot be specified with the -S option.

    -S servicedir

    Specifies an alternate service directory. Use to apply MU1 to a service area for clients of a different operating system or architecture than the server. Cannot be specified with the -R option.

    When the installation is complete, the following message is displayed:


    install_mu completed successfully.

    • If you see this message, go to Steps 9 and 10 to complete the installation.

    • If you encounter any errors, go to Step 11.

  9. Reboot the system by typing:


    # sync ; reboot

    You are then prompted for a login.

    Note -

    It is very important that you reboot your system after installing MU1 to prevent the library conflict problem.

  10. Type your login name and password:


    login: login
password: password

  11. If you encounter errors, check the detail log file for error information.

    Errors encountered during patch installation are displayed after installation is complete. Check the detail log file for additional information about any patches or packages that were not installed. 


    # more \
$rootdir/var/sadm/install_data/Maintenance_Update_log.mu_version_name.date_time

    where:

    • $rootdir is the root directory of the system that you have just updated; for example, / for the local system and /export/root/clientname for a diskless client.

    • mu_version_name is the name of the MU (it is Solaris_7MU1 for MU1).

    • date_time is the designated date and time copied from date +%y%m%d%H%M%S ( yyyymmddHHMMSS or year-month-day-hour-minute-second).

    Note -

    $rootdir/var/sadm/install_data/Maintenance_Update_log is a symbolic link to the most recent MU log file.

    For explanations and recommended actions for error codes, see Appendix A.

Backing Out

The patches in the Solaris 7 MU1 software have been tested together as a set and, for the greatest stability, should be used that way. If you need to remove one of the patches, you may do so provided that you did not use the -d option of install_mu during the installation of the Solaris 7 MU1 software.

Instructions for backing out individual patches are located in each patch directory. Patch directories are located in $rootdir/var/sadm/patch/.

Note -

Backing out the entire MU is not possible if you selected the -d option of install_mu.

It is best to reboot your system in single-user mode before backing out the MU1. MU1 patches system libraries. On a multi-user system, your system will be unstable if any processes have mapped to a patched version of a library and later attempt to map to different sections of the old library.

In single-user mode, network services are not available. If the MU1 image is on the network rather than on a CD, you must copy the MU1 image from the network to your local system before booting your system in single-user mode.

If it is not possible to reboot the system in single-user mode or if you do not have enough disk space to make a local copy of the MU1 image, you will need to back out MU1 using NFS in multi-user mode. In this case, you should have the system in as quiet a state as possible without users logged on or running jobs.

The backout_mu script provided by MU1 enables you to back out an entire MU. To back out the Solaris 7 MU1 software:

  1. Make sure that no important user or system processes are running.

  2. Exit the current session.

    The CDE login screen appears.

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

    The system prompts you to login.

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


    login: root
password: root password

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


    # reboot -- -s
    Note -

    Changing the run level from multi-user mode to single-user mode with the shutdown or init command might leave the vold process running. This may cause problems mounting the MU1 CD in single-user mode.

  6. Enter 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.7 Generic October 1998
#

    • If you are running backout_mu from the CD, go to Step 7.

    • If you are running backout_mu from a local copy of the MU1 image, go to Step 8.

  7. To mount the MU1 CD, place the CD in the drive and from the root shell prompt, type:


    # mount -o ro -F hsfs /dev/dsk/c0t6d0s0 /cdrom
    Note -

    In some cases, the CD-ROM drive may be on a different controller than c0 or a different target than t6, which would require a different path to the CD-ROM device. Check with your system administrator if you have questions about mounting the CD-ROM drive.

  8. Run backout_mu.

    • From a local copy of the MU1 image, type:


      # cd local_directory
# ./backout_mu any desired options

    • From the MU1 CD, type:


      # cd /cdrom
# ./backout_mu any desired options
    Table 2-2 Command Line Options for backout_mu

    Option 

    Description 

    -T tooldir

    Specifies the location of the patch tools directory. 

    -q

    Disables the display of dots that indicate install_mu activity.

    -B backoutdir

    Specifies an alternate directory in which patches have been saved. 

    -R rootdir

    Specifies an alternate root directory. 

    -S servicedir

    Specifies an alternate service directory. 

    When the back out is complete, the following message is displayed:


    backout_mu completed successfully.

    • If you see this message, go to Steps 9 and 10 to complete the back out.

    • If you encounter any errors, go to Step 11.

  9. Reboot the system by typing:


    # sync ; reboot

    You are then prompted for a login.

    Note -

    It is very important that you reboot your system after backing out MU1 to prevent the library conflict problem.

  10. Type your login name and password:


    login: login
password: password

  11. If you encounter errors, check the detail log file for error information.

    Errors encountered during patch back out are displayed after back out has been completed. Check the detail log file for additional information about any patches or packages that were not backed out. 


    # more \
$rootdir/var/sadm/install_data/MU_Backout_log.mu_version_name.date_time

    where:

    • $rootdir is the root directory of the system that you have just updated; for example, / for the local system and /export/root/clientname for a diskless client.

    • mu_version_name is the name of the MU ( it is Solaris_7MU1 for MU1).

    • date_time is the designated date and time copied from date +%y%m%d%H%M%S (i.e., yyyymmddHHMMSS or year-month-day-hour-minute-second).

    Note -

    $rootdir/var/sadm/install_data/Maintenance_Backout_log is a symbolic link to the most recent MU log file.

    For explanations and recommended actions for error codes, see Appendix A.

Installing on a Diskless Client or Solstice AutoClient from a Server

You can install the Solaris 7 MU1 software on a diskless client or Solstice AutoClient from a server that is in multiuser mode. However, you cannot run install_mu before you add a client. Refer to Solaris 7 Installation Library for details on using SolsticeTM AdminSuiteTM.

You need to decide whether to use admclientpatch or install_mu to install the Solaris 7 MU1 software in a client/server environment. Use the following table and discussion to decide which method to use:

Table 2-3 Differences between admclientpatch and install_mu
 

admclientpatch

install_mu

Patching speed 

Slower 

Faster 

Service area handling 

Automatic 

Manual 

Ease of patching 

More involved 

Simple 

Integration with AdminSuite 

Complete 

None 

admclientpatch is an AdminSuite utility that manages the installation and removal of a collection of patches on a set of managed clients. Applying the MU patch set via install_mu bypasses AdminSuite's patch management process and makes it more difficult later to manage the patch set shared by multiple clients. This is a concern if the number of clients is large or if patches other than those in the MU set are installed or removed.

admclientpatch automatically patches client service areas. With install_mu, each client needs to be patched with the -R option, then install_mu must be executed with the -S option for each service area. If there are multiple clients that share a single service area, you only need to run install_mu once with the -S option. This procedure ensures that both the service area and root area of a client remain consistent.

install_mu patches clients more quickly because it bypasses the admclientpatch patch management process and because admclientpatch removes older revisions of patches before applying newer ones. In environments with few clients and service areas, install_mu may be a good way to patch clients and service areas.

install_mu may be easier to use because it recognizes the MU set of patches. The MU distribution patch directory contains a file (.order) that lists all of the patches it will apply in the correct order, considering patch requirements. To patch clients with admclientpatch, write a script that reads the .order file, applies the patches to the admclientpatch spool area, and then invokes admclientpatch to install the patches to the clients. Run install_mu with the -D (dry run) option to identify the location of the .order file.

For more information about managing clients and patches, see the Solstice AutoClient 2.1 Administration Guide at http://docs.sun.com

Note -

install_mu supports installations on servers with both homogeneous and heterogeneous server/client root paths. It also supports installing on a server's service area for either heterogeneous or homogeneous clients.

Installing With install_mu

To install the Solaris 7 MU1 software on a diskless client or AutoClient from a server using install_mu:

  1. Halt the diskless client or AutoClient.

  2. On the server, run the install_mu script located in the local product directory, with the client's root directory as the argument.

    • From a local copy of the MU1 image that corresponds to the client platform, type:


      # cd local_directory
# ./install_mu -R /export/root/client_name

      where client_name is the hostname of the diskless client or AutoClient.

    • From the MU1 CD, mount the CD and type:


      # cd /cdrom/S7_maintenance_update_1_x86
# ./install_mu -R /export/root/client_name

      where client_name is the hostname of the diskless client or AutoClient.

  3. Repeat this process for each diskless client or AutoClient being served.

  4. Install the Solaris 7 MU1 software on the server's service area. From a local copy of the MU1 image that corresponds to the server platform, type:


    # cd local_directory
# ./install_mu -S Solaris_2.7

  5. Boot the diskless client or AutoClient.

Backing Out With backout_mu

To back out the Solaris 7 MU1 software on a diskless client or AutoClient from a server using backout_mu:

  1. Halt the diskless client or AutoClient.

  2. On the server, run the backout_mu script located in the local product directory, with the client's root directory as the argument.

    • From a local copy of the MU1 image that corresponds to the client platform, type:


      # cd local_directory
# ./backout_mu -R /export/root/client_name

      where client_name is the hostname of the diskless client or AutoClient.

    • From the MU1 CD, mount the CD and type:


      # cd /cdrom/S7_maintenance_update_1_x86
# ./backout_mu -R /export/root/client_name

      where client_name is the hostname of the diskless client or AutoClient.

  3. Repeat this process for each diskless client or AutoClient being served.

  4. Back out the Solaris 7 MU1 software on the server's service area. From a local copy of the MU1 image that corresponds to the server platform, type:


    # cd local_directory
./backout_mu -S Solaris_2.7

  5. Boot the diskless client or AutoClient.

Identifying the Version of Your Solaris 7 Maintenance Update

To identify the version of your Solaris 7 MU software, type:


# cat /etc/release