test

Solaris 7 Maintenance Update 4 Release Notes

Chapter 3 Backing Out the Solaris 7 Maintenance Update 4

The patches in the Solaris 7 MU4 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 MU4 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 AutoClient systems, 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.

Backing Out on a Standalone System

It is best to reboot your system in single-user mode before backing out the MU4. MU4 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 MU4 image is on the network rather than on a CD, you must copy the MU4 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 MU4 image, you will need to back out MU4 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 MU4 enables you to back out an entire MU. To back out the Solaris 7 MU4 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 when mounting the MU4 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. Determine whether you must back out special patches.

    • If you did not install special patches as described in "Installing Special Patches", go to Step 8 to complete the backout.

    • If you installed special patches as described in "Installing Special Patches", you must back out the special patches by typing the following command for each of the patches:


      # patchrm patch_id

      where patch_id is the ID of the special patch.

  8. Determine where you are running the backout_mu command.

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

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

  9. To mount the MU4 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.

  10. Run backout_mu.

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


      # cd local_directory
# ./backout_mu any desired options

    • From the MU4 CD, type:


      # cd /cdrom
# ./backout_mu any desired options
    Table 3-1 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.

  11. 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 MU4 to prevent the library conflict problem.

  12. Type your login name and password:


    login: login
password: password

Backing Out on a Diskless Client or Solstice AutoClient from a Server

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

  1. Halt the diskless client or AutoClient system.

  2. Determine whether you must back out special patches.

    • If you did not install special patches on a diskless client or Solstice AutoClient system as described in "Installing Special Patches" , go to Step 3 to complete the backout.

    • If you installed special patches on a diskless client or Solstice AutoClient system, as described in "Installing Special Patches", you must back out the special patches by typing the following command for each of the patches:


      # patchrm -R /export/root/client_name patch_id

      where client_name is the hostname of the diskless client or AutoClient system and patch_id is the ID of the special patch.

  3. 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 MU4 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 MU4 CD, mount the CD and type:


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

      where platform is sparc or x86 and client_name is the hostname of the diskless client or AutoClient system.

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

  5. Determine whether you must back out special patches.

    • If you did not install special patches on a server's service area, as described in "Installing Special Patches" , go to Step 6 to complete the backout.

    • If you installed special patches on a server's service area, as described in "Installing Special Patches", you must back out the special patches by typing the following command for each of the patches:


      # patchrm -S Solaris_2.7 patch_id

      where patch_id is the id of the special patch.

  6. Back out the Solaris 7 MU4 software on the server's service area. From a local copy of the MU4 image that corresponds to the service area being patched, type:


    # cd local_directory
./backout_mu -S Solaris_2.7
    Note -

    If a service area is shared by the server, you also need to remove the same Maintenance Update patch set from the server's root area. Failure to do so will result in an unstable and improperly patched server.

  7. Boot the diskless client or AutoClient system.

Backing Out Patches That Support Net Installs and Custom JumpStart

As described in "Installing Patches That Support Net Installs and Custom JumpStart", MU4 contains several patches that correct problems with Interactive Install and Custom JumpStart. If you installed these patches, you may back out the patches using the following command:


# patchrm path_to_OS_image/Solaris_2.7/Tools/Boot patch_id

where patch_id is the ID of the patch to back out. See Table 2-5 and Table 2-6 for lists of patch IDs.