Installing on a Diskless Client or Solstice AutoClient from a Server

You can install the Solaris 7 MU1 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 MU1 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 supports installations on servers with both homogeneous and heterogeneous server/client root paths. It also supports installing on a server's service area for either heterogeneous or homogeneous clients.

Installing With install_mu

To install the Solaris 7 MU1 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 MU1 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 MU1 CD, mount the CD and type:

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

     where 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 MU1 software on the server's service area. From a local copy of the MU1 image that corresponds to the server platform, type:

   # cd local_directory # ./install_mu -S Solaris_2.7

5. Boot the diskless client or AutoClient.

Backing Out With backout_mu

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

1. Halt the diskless client or AutoClient.

2. 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 MU1 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 MU1 CD, mount the CD and type:

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

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

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

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

   # cd local_directory ./backout_mu -S Solaris_2.7

5. Boot the diskless client or AutoClient.