This chapter describes how to install your Solaris 9 MU3 software. If you are installing the Solaris 9 MU3 software as part of a custom JumpStartTM installation, refer to the Solaris 9 Installation Guide.
The Solaris 9 MU3 installation time varies, depending on the following:
CPU speed of your machine
install_mu option that you select
Transfer speed of the hard drive or network that you use to access the install_mu code and patch set
If you install the MU3 with the -d option disabled, installation proceeds more quickly. However, you cannot then back out any of the patches MU3 delivers.
The MU3 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:
Whether you select the -d option
The location of the backout directory when saving backout data
The disk partitions and the space that is available in each file system, relative to the patch disk space that is needed for each file system
Your system's locale
Whether some of the Maintenance Update patches are already installed on your system
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 it 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 install_mu with the -f option if you meet both of the following conditions:
You know that you have enough disk space to apply the patch set and backout data if desired
If you are bypassing the space calculation
Solaris 9 MU3 software can only be installed if the system that is running install_mu is already running the Solaris 9 operating environment.
Relocatable root and service areas are not supported in the Solaris 9 MU3.
Ideally, you reboot your system in single-user mode before installing MU3 because MU3 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 copy the MU3 image from the network to your local system before booting your system in single-user mode.
You need to install MU3 by using NFS in multiuser mode if you meet one of the following criteria:
You cannot reboot the system in single–user mode
You do not have enough disk space to make a local copy of the MU3 image
In this case, you should have the system in as quiet a state as possible, without users logged on or running jobs.
When in single-user mode or multiuser mode, you must reboot your system after MU3 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 detail.
Ensure that you have backed up your system's operating system before proceeding.
To install the Solaris 9 MU3 software perform the following steps:
Ensure that no important user or important system processes are running.
You must kill the powerd process if it is running.
Exit the current session.
The CDE login screen is displayed.
Click the Options button and select Command Line Login.
The system prompts you to log in.
Type your login name as root and type the root password:
login: root password: root password |
Reboot in single-user mode. From the root shell prompt, type:
# reboot -- -s |
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 # |
Run install_mu. From a local copy of the MU3 image, type:
# cd local_directory # ./install_mu options |
You can use the following options at the command line.
Table 2–1 Command-Line Options for install_mu
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. |
When the installation is complete, check that the following message is displayed.
install_mu completed at date_time. |
If you see this message, go to Step 9.
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.
To prevent the library conflict problem, you must reboot your system after installing MU3.
Type your login name and password:
login: login password: password |
To identify the version of your Solaris 9 MU software, type:
# cat /etc/release |
To identify the patches the MU software applied to your system, type:
# showrev -p |
If you compare the showrev -p output from applying the Solaris 9 MU3 software to the showrev -p output from installing the Solaris 9 4/03 operating environment, you will note that the following patches are not applied in the MU3 installation.