test

Solaris 7 Maintenance Update 1 Release Notes (SPARC Platform Edition)

Installing Maintenance Update 1

Solaris 7 MU1 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 MU1 because MU1 patches system libraries. On a multi-user system, your 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 MU1 image is on the network rather than on a CD, you must copy the MU1 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 MU1 image, you will need to install MU1 using NFSTM in multi-user mode. In this case, you should have the system in as quiet a state as possible, without users logged or running jobs.

Note -

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

To install the Solaris 7 MU1 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 login.

  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 MU1 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 MU1 image, go to Step 8.

  7. To mount the MU1 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 different controller than c0 or a different target 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 MU1 image, type:


      # cd local_directory
# ./install_mu any desired options

    • From the MU1 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 

    -u

    Unconditional install; does not verify that files to be updated were not changed since the initial installation. 

    -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. Cannot be specified with the -D option.

    -D

    Dry run mode; reports the amount of needed disk space without applying patches. Cannot be specified with -f option.

    -R rootdir

    Specifies an alternate root directory. Use to apply MU1 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 MU1 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 is displayed:


    install_mu completed successfully.

    • If you see this message, go to Steps 9 and 10 to complete the installation.

    • If you encounter any errors, go to Step 11.

  9. 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 MU1 to prevent the library conflict problem.

  10. Type your login name and password:


    login: login
password: password

  11. If you encounter errors, check the detail log file for error information.

    Errors encountered during patch installation are displayed after installation is complete. Check the detail log file for additional information about any patches or packages that were not installed. 


    # more \
$rootdir/var/sadm/install_data/Maintenance_Update_log.mu_version_name.date_time

    where:

    • $rootdir is the root directory of the system that you have just updated; for example, / for the local system and /export/root/clientname for a diskless client.

    • mu_version_name is the name of the MU (it is Solaris_7MU1 for MU1).

    • date_time is the designated date and time copied from date +%y%m%d%H%M%S ( yyyymmddHHMMSS or year-month-day-hour-minute-second).

    Note -

    $rootdir/var/sadm/install_data/Maintenance_Update_log is a symbolic link to the most recent MU log file.

    For explanations and recommended actions for error codes, see Appendix A.