Installing on a Diskless Client or Solstice AutoClient from a Server

You can install the Solaris 7 MU2 software on a diskless client or Solstice AutoClient from a server that is in multiuser mode. However, you cannot run install_mu before you add a client. Refer to Solaris 7 Installation Library for details on using Solstice^TM AdminSuite^TM.

You need to decide whether to use admclientpatch or install_mu to install the Solaris 7 MU2 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 AdminSuite's patch management process and makes it more difficult later 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. Run install_mu with the -D (dry run) option to identify the location of the .order file.

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 MU2 can only be installed on a system that is running the Solaris 7 operating environment. In a client/server environment, the MU2 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 MU2 software on a diskless client or AutoClient from a server using install_mu:

1. Halt the diskless client or AutoClient.

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 MU2 image that corresponds to the client platform, type:

     # cd local_directory # ./install_mu -R /export/root/client_name

     where client_name is the hostname of the diskless client or AutoClient.

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

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

     where platform is sparc or x86 and client_name is the hostname of the diskless client or AutoClient.

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

4. Install the Solaris 7 MU2 software on the server's service area. From a local copy of the MU2 image that corresponds to the server platform, 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. Check to see if you need to install special patches as described in "Installing Special Patches on a Diskless Client or Solstice AutoClient from a Server."

6. Boot the diskless client or AutoClient.

Installing Special Patches on a Diskless Client or Solstice AutoClient from a Server

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

To determine if these additional patches should be applied to your system, check the /etc/release file for the release date by typing:

# cat /export/root/client_name/etc/release

If your screen displays this version of the Solaris operating environment, you must apply special patches.

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

1. Change directory to the special patch directory by typing:

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

     # cd local_directory/Solaris_7_MU2/platform/Patches/special_patches

   • From the MU2 CD, type:

     # cd /cdrom/Solaris_7_MU2/platform/Patches/special_patches

   where platform is either sparc or i386.

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

   • For each client root area:

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

   • For the service area:

     # patchadd -S Solaris_2.7 -M . patchlist

   The patches contained in the Special Patch directory for the SPARC platform of the MU2 include:

   107612-01	SunOS 5.7	koi8-R -ow hung before dtlogin screen
   107616-01	SunOS 5.7	European locale updates
   107693-01	SunOS 5.7	l10n_euro message updates for SUNW* is SUNW*os 599
   107707-01	SunOS 5.7	WOS Message Updates

   The patches contained in the Special Patch directory for the x86 platform of the MU2 include:

   107613-01	SunOS 5.7_x86	koi8-R -cde and ow hung before dtlogin screen
   107617-01	SunOS 5.7_x86	European locale updates
   107694-01	SunOS 5.7_x86	l10n_euro message updates for SUNW*is SUNW*os 599
   107708-01	SunOS 5.7_x86	WOS Message Updates

3. Return to Step 6 in "Installing With install_mu" to complete the installation.

Backing Out With backout_mu

To back out the Solaris 7 MU2 software on a diskless client or AutoClient from a server using backout_mu:

1. Halt the diskless client or AutoClient.

2. If you are running the Solaris 7 operating environment on your system and have installed special patches on a diskless client or a Solstice AutoClient, as described in "Installing Special Patches on a Diskless Client or Solstice AutoClient from a Server," then you must back out patches individually, as described in "Backing Out Special Patches on a Diskless Client or Solstice AutoClient from a Server."

3. On the server, run the backout_mu script located in the local product directory, with the client's root directory as the argument.

   • From a local copy of the MU2 image that corresponds to the client platform, type:

     # cd local_directory # ./backout_mu -R /export/root/client_name

     where client_name is the hostname of the diskless client or AutoClient.

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

     # cd /cdrom/s7_maintenance_update_2_platform # ./backout_mu -R /export/root/client_name

     where platform is sparc or x86 and client_name is the hostname of the diskless client or AutoClient.

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

5. If you are running the Solaris 7 operating environment on your system and have installed special patches on a server's service area, as described in "Installing Special Patches on a Diskless Client or Solstice AutoClient from a Server," then you must back out patches individually, as described in "Backing Out Special Patches on a Diskless Client or Solstice AutoClient from a Server."

6. Back out the Solaris 7 MU2 software on the server's service area. From a local copy of the MU2 image that corresponds to the server platform, type:

   ---

   Note -

   If you are backing out the MU2 from a server's service area on a SPARC server that has x86 clients, refer to bug ID 4228999 in "Backout Bugs".

   ---

   # cd local_directory ./backout_mu -S Solaris_2.7

   ---

   Note -

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

   ---

7. Boot the diskless client or AutoClient.

Backing Out Special Patches on a Diskless Client or Solstice AutoClient from a Server

For a Client Root Area

1. Type the following command for each patch that you must back out.

   # patchrm -R /export/root/client_name patch_id Checking installed packages and patches... Backing out patch patch_id ...

   where patch_id is the id of the special patch.

2. Return to Step 3 in the "Backing Out With install_mu" section to complete the client backout process.

For a Server's Service Area

1. Type the following command for each patch that you must back out.

   # patchrm -S Solaris_2.7 patch_id Checking installed packages and patches... Backing out patch patch_id ...

   where patch_id is the id of the special patch.

2. Return to Step 6 in the "Backing Out With install_mu" section to complete the server's service area backout process.