This chapter describes how to install your Solaris 8 MU1 software. If you want to install the Solaris 8 MU1 software as part of a custom JumpStartTM installation, refer to the Solaris 8 Advanced Installation Guide.
The Solaris 8 MU1 installation procedure is faster than the installation of the individual MU1 patches. The Solaris 8 MU1 installation time varies depending on:
CPU speed of your machine
install_mu option you select
Transfer speed of the CD-ROM drive, hard drive, or network you use to access the install_mu code and patch set
If you install the MU1 with the backout option disabled, installation will proceed more quickly. However, you will not be able to back out any of the patches MU1 delivers.
The MU1 may only be installed on a system running the Solaris 8 operating environment.
Space requirements per file system vary depending on:
Whether you select the backout option
The location of the backout directory when saving backout data
The disk partitions and the space available in each file system versus the patch disk space needed per 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 for you and reports the space needed per file system, including back out space if applicable. The space calculations take several minutes to complete.
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 backout data space need is estimated and the reported need may be higher than the actual need.
If you are certain that you have enough space to apply the patch set (and backout data if desired) and you want to bypass the space calculation, run install_mu with the -f option.
Solaris 8 MU1 software can only be installed if both the system running install_mu and the target systems are already running the Solaris 8 operating environment.
It is best to reboot your system in single-user mode before installing MU1 because MU1 applies patches to system libraries. Individual systems in a multiuser 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 NFS in multiuser mode. In this case, you should have the system in as quiet a state as possible, without users logged on or running jobs.
Be sure that you have backed up your system's operating system before proceeding.
To install the Solaris 8 MU1 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 type the root password:
login: root password: root password |
Reboot in single-user mode. From the root shell prompt, type:
# reboot -- -s |
Changing the run level from multiuser mode to single-user mode with the shutdown or init command might leave the vold process running. This process can cause problems mounting the MU1 CD in single-user mode.
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.8 Generic Feb 2000 # |
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 |
In some cases the CD-ROM drive might 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 install_mu.
From a local copy of the MU1 image, type:
# cd local_directory # ./install_mu options |
From the MU1 CD, type:
# cd /cdrom # ./install_mu options |
You can use the following options on the command line.
Table 2-1 Command-Line Options for install_mu
Option |
Description |
---|---|
-d |
Specifies that patches will not be backed up. Using 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. Using this option saves time, but you must use it only if you are certain that you have enough space. |
When the installation is complete, the following message appears.
install_mu completed successfully. |
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 MU1.
Type your login name and password:
login: login password: password |
To identify the version of your Solaris 8 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 8 MU1 software to the showrev -p output from installing the Solaris 8 6/00 operating environment, you will note that the following patches are not applied in the MU1 installation:
Solaris 8 MU1 SPARC Platform Edition:
108631-06
109316-01
Solaris 8 MU1 Intel Platform Edition:
108632-06
These patches are needed to generate the Solaris 8 6/00 operating environment, but are not needed to apply the Solaris 8 MU1 patches.