test

Solaris 7 Maintenance Update 4 Release Notes

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

Table 2-2 Differences Between admclientpatch and install_mu
 

admclientpatch

install_mu

Patching speed 

Slower 

Faster 

Service area handling 

Automatic 

Manual 

Ease of patching 

More involved 

Simple 

Integration with AdminSuite 

Complete 

None 

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:

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.

Note -

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.