Solaris 7 Maintenance Update 4 Release Notes

Installing Maintenance Update 4 on a Standalone System

Solaris 7 MU4 software can only be installed if both the system running install_mu and the target systems are already running Solaris 7.

It is best to reboot your system in single-user mode before installing MU4 because MU4 applies patches to system libraries. Individual systems in a multi-user 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 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 install 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.

Note -

Be sure that you have backed up your system's operating system before proceeding.

If a system shares a service area with any diskless clients or Solstice AutoClient systems, you need to invoke install_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 applied correctly.

To install 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 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 #
- If you are running install_mu from the CD, go to Step 7.
- If you are running install_mu from a local copy of the MU4 image, go to Step 8.

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 install_mu.

From a local copy of the MU4 image, type:

# cd local_directory
# ./install_mu any desired options

From the MU4 CD, type:

# cd /cdrom
# ./install_mu any desired options

The following options can be used 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 it takes 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 back out data is saved in the indicated directory. Cannot be specified with the `-d` option.
`-f`	Force installation of patch set without checking for sufficient disk space. Using this option saves time, but you should only use it if you are certain that you have enough space.
`-R` `rootdir`	Specifies an alternate root directory. Use to apply MU4 to clients whose package system information files are located in a directory tree starting in the specified `rootdir`. Cannot be specified with the `-S` option.
`-S` `servicedir`	Specifies an alternate service directory. Use to apply MU4 to a service area for clients of a different operating system or architecture than the server. Cannot be specified with the `-R` option.

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.

Identify the Solaris release running on your system by typing:

# cat /etc/release

You will see a display showing the Solaris platform version and date.

 
                            Solaris 7 s998_21al2b SPARC
            Copyright 1998 Sun Microsystems, Inc.  All Rights Reserved.
                             Assembled 06 October 1998

Compare the Solaris platform version and date displayed to the table below to determine if you need to install special patches.

	October 1998	January 1999	April 1999	July 1999
SPARC	Yes, install special patches	No, do not install special patches	No, do not install special patches	No, do not install special patches
Intel	Yes, install special patches	Yes, install special patches	No, do not install special patches	No, do not install special patches

If you must install special patches, go to "Installing Special Patches" to complete the installation.
If you do not need to apply special patches, go to Step 10 to complete the installation.

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

Type your login name and password:
login: login password: password