Chapter 2 Installing the Solaris 7 Maintenance Update 4

This chapter describes how to install your Solaris 7 MU4 software on a standalone system or on a diskless client or Solstice^TM AutoClient^TM system from a server. If you want to install the Solaris 7 MU4 software as part of a customized JumpStart^TM (automatic installation) process, refer to the Solaris Advanced Installation Guide.

Time Considerations

The Solaris 7 MU4 installation procedure takes much less time than it takes to install the MU4 patches individually. The Solaris 7 MU4 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 MU4 with the backout option disabled, installation will proceed more quickly. However, you will not be able to back out any of the patches MU4 delivers.

Requirements

The MU4 may only be installed on a system running the Solaris 7 operating environment. In a client/server environment, the MU4 can only be applied to a client if both the client and server are running the Solaris 7 operating environment.

Space requirements per file system vary depending on:

• Whether you select the back out option

• The location of the back out 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

• Whether you are patching a client, a server, or a service area

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 back out 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 back out data if desired) and you want to bypass the space calculation, run install_mu with the -f option.

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.

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:

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 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 #

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

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

   ---

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

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

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

    ---

11. Type your login name and password:

    login: login password: password

Installing on a Diskless Client or Solstice AutoClient from a Server

You can install the Solaris 7 MU4 software on a diskless client or Solstice AutoClient system from a server that is in multiuser mode. However, you cannot run install_mu before you add a client. While it is possible to install the MU4 software in multiuser mode, it is best to reboot your system in single-user mode before installing MU4. Refer to Solaris 7 Installation Library for details on using the Solstice^TM AdminSuite^TM product.

You need to decide whether to use admclientpatch or install_mu to install the Solaris 7 MU4 software in a client/server environment. Use the following table and discussion to decide which method to use.

admclientpatch is an AdminSuite utility that manages the installation and removal of a collection of patches on a set of managed clients. Applying the MU patch set via install_mu bypasses the AdminSuite product's patch management process and makes it more difficult to manage the patch set shared by multiple clients. This is a concern if the number of clients is large or if patches other than those in the MU set are installed or removed.

admclientpatch automatically patches client service areas. With install_mu, each client needs to be patched with the -R option, then install_mu must be executed with the -S option for each service area. If there are multiple clients that share a single service area, you only need to run install_mu once with the -S option. This procedure ensures that both the service area and root area of a client remain consistent.

install_mu patches clients more quickly because it bypasses the admclientpatch patch management process and because admclientpatch removes older revisions of patches before applying newer ones. In environments with few clients and service areas, install_mu may be a good way to patch clients and service areas.

install_mu may be easier to use because it recognizes the MU set of patches. The MU distribution patch directory contains a file (.order) that lists all of the patches it will apply in the correct order, considering patch requirements. To patch clients with admclientpatch, write a script that reads the .order file, applies the patches to the admclientpatch spool area, and then invokes admclientpatch to install the patches to the clients. You will find the .order file:

• On a local copy of the MU4 image in the local_directory/Solaris_7_MU4/platform/Patches directory

• On the MU4 CD in the /cdrom/Solaris_7_MU4/platform/Patches directory

where platform is either sparc or i386.

For more information about managing clients and patches, see the Solstice AutoClient 2.1 Administration Guide at http://docs.sun.com.

install_mu can be installed on servers that support SPARC and x86 server or client root paths. It can also be installed in a server's service area for either SPARC or x86 clients. The MU4 can only be installed on a system that is running the Solaris 7 operating environment. In a client/server environment, the MU4 can only be installed on a client if both the client and the server are running the Solaris 7 operating environment.

Installing With install_mu

To install the Solaris 7 MU4 software on a diskless client or AutoClient system from a server using install_mu:

1. Halt the diskless client or AutoClient system.

2. On the server, run the install_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 # ./install_mu -R /export/root/client_name

     where client_name is the host name of the diskless client or AutoClient system.

   • From the MU4 CD, mount the CD and type:

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

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

3. Repeat this process for each diskless client or AutoClient system being served.

4. Install 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 # ./install_mu -S Solaris_2.7

   ---

   Note -

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

   ---

5. 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 6 to complete the installation.

6. Boot the diskless client or AutoClient system.

Installing Special Patches

Some MU4 patches are not automatically installed on systems running the Solaris 7 and Solaris 7 3/99 operating environments. The patch set that is included in the MU4 is complete only for systems running the Solaris 7 5/99 and 8/99 operating environments. If you want to apply MU4 patches to systems running the Solaris 7 or Solaris 7 3/99 operating environments, you will need to apply additional patches.

The special patches for the Solaris SPARC Platform Edition of the MU4 include:

The special patches for the Solaris Intel Platform Edition of the MU4 include:

If you determined during the installation that you need to apply special patches, follow the steps below that correspond to the type of installation you are performing:

• "Installing Special Patches on a Standalone System"

• "Installing Special Patches on a Diskless Client or Solstice AutoClient"

You may choose to install all of the special patches or only the special patches that apply to your system. Review the special patch descriptions to determine which patches apply to your system. For a more detailed description of each patch, refer to the individual patch readmes.

Installing Special Patches on a Standalone System

1. Change directory to the special patch directory.

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

     # cd local_directory/Solaris_7_MU4/platform/Patches/special_patches

   • From the MU4 CD, type:

     # cd /cdrom/Solaris_7_MU4/platform/Patches/special_patches

   where platform is either sparc or i386.

2. Install the special patches.

   • To install all of the special patches:

     # patchadd -M . patchlist

   • To install specific special patches, type the following command:

     # patchadd -M . patch_id patch_id

     where patch_id is the id of the special patch to install. You may install more than one patch by including each patch id in the command.

3. 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 as described in "Installing Maintenance Update 4 on a Standalone System".

   ---

4. Type your login name and password:

   login: login password: password

Installing Special Patches on a Diskless Client or Solstice AutoClient

1. Change directory to the special patch directory.

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

     # cd local_directory/Solaris_7_MU4/platform/Patches/special_patches

   • From the MU4 CD, type:

     # cd /cdrom/Solaris_7_MU4/platform/Patches/special_patches

   where platform is either sparc or i386.

2. Install the special patches using the following commands accordingly:

   • For each client root area:

     • To install all of the special patches:

       # patchadd -R /export/root/client_root -M . patchlist

     • To install specific special patches, type the following command:

       # patchadd -R /export/root/client_root -M . patch_id patch_id

       where patch_id is the id of the special patch to install. You may install more than one patch by including each patch id in the command.

   • For the service area:

     • To install all of the special patches:

       # patchadd -S Solaris_2.7 -M . patchlist

     • To install specific special patches, type the following command:

       # patchadd -S Solaris_2.7 -M . patch_id patch_id

       where patch_id is the id of the special patch to install. You may install more than one patch by including each patch id in the command.

3. Boot the diskless client or AutoClient system.

Installing Patches That Support Net Installs and Custom JumpStart

MU4 contains several patches that correct problems with Interactive Install and Custom JumpStart. If you have servers that support Solaris 7 Net Install, install the patches that correspond to the OS images located on the Net Install servers.

The patches affect the miniroot (the files located under Tools/Boot on the OS image) and are installed differently than other Solaris patches.

The miniroot is found on full Net Install servers and Boot servers. You must patch the miniroot in both locations. If you patch a Net Install server and subsequently make a Boot server from it using the setup_install_server command, the new Boot server incorporates the patch applied to the Net Install server.

To install the patches:

1. Change directory to the Net Install patches directory.

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

     # cd local_directory/Solaris_7_MU4/platform/Patches/netinstall_patches

   • From the MU4 CD, type:

     # cd /cdrom/Solaris_7_MU4/platform/Patches/netinstall_patches

   where platform is either sparc or i386

2. Install the patches using the following command:

   # patchadd -C path_to_OS_image/Solaris_2.7/Tools/Boot -M . patchlist

Identifying the Version of Your Solaris 7 Maintenance Update

To identify the version of your Solaris 7 MU software, type:

# cat /etc/release