test

Solaris 7 Maintenance Update 2 Release Notes

Backing Out

The patches in the Solaris 7 MU2 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 MU2 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.

If a system shares a service area with any diskless clients or Solstice AutoClients, you need to invoke backout_mu again with the -R option for each client using the service area. Failure to do so makes the client unstable because patches have not been backed out correctly.

It is best to reboot your system in single-user mode before backing out the MU2.MU2 applies patches to system libraries. Individual systems in a multi-user 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 MU2 image is on the network rather than on a CD, you must copy the MU2 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 MU2 image, you will need to back out MU2 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 MU2 enables you to back out an entire MU. To back out the Solaris 7 MU2 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 log in.

  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 MU2 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
#

  7. If you are running the Solaris 7 operating environment on your system and have installed special patches, as described in "Installing Special Patches", then you must back out patches individually, as described in "Backing Out Special Patches".

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

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

  8. To mount the MU2 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 controller other than c0 or a target other 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.

  9. Run backout_mu.

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


      # cd local_directory
# ./backout_mu any desired options

    • From the MU2 CD, type:


      # cd /cdrom
# ./backout_mu any desired options
    Table 2-3 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 backout_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 10 and 11 to complete the back out.

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

  10. 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 MU2 to prevent the library conflict problem.

  11. Type your login name and password:


    login: login
password: password

  12. 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_7MU2 for MU2).

    • 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/MU_Backout_log is a symbolic link to the most recent MU log file.

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