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:
-
Make sure that no important user or system processes are running.
-
Exit the current session.
The CDE login screen appears.
-
Click the Options button and select Command Line Login.
The system prompts you to log in.
-
Type your login name as root and enter the root password:
login: root password: root password
-
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.
-
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
-
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.
-
-
Determine where you are running the backout_mu command.
-
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.
-
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
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 Step 11 to complete the back out.
-
If you encounter any errors, go to Chapter 5, Error Messages.
-
-
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.
-
Type your login name and password:
login: login password: password
- © 2010, Oracle Corporation and/or its affiliates