Solaris 8 Maintenance Update 5 Installation Guide

Chapter 4 Known Problems

This chapter describes known problems relating to the installation and use of the Solaris 8 MU5 software.

Installation Bugs

install_mu Does Not Function Correctly When Starting It Using sh (4062334)

Because of problems regarding the interactions between sh(1) and ksh(1), the install_mu utility might fail to install certain patches correctly when you start it using the following command from the command line or from an administrative script:

# /bin/sh ./install_mu options

Workaround: Execute install_mu from the command line or from an administrative script as follows:

# ./install_mu options

Patchadd Displays an Error That It Is Terminating

One of the following benign messages might be displayed by install_mu:

One or more patch packages included in
XXXXXX-YY are not installed on this system.

Patchadd is terminating.


Installation of XXXXXX-YY failed:
  Attempting to patch a package that is not installed.

These messages indicate that patchadd could not find on your system any of the packages that it intended to patch, so it skipped the indicated patch.

The message is displayed when patchadd notices a discrepancy installing a patch of one architecture onto a system with a different architecture (for example, a sun4u patch on a sun4m system.)

This may also be the result of one or more missing packages. The package might have been removed by the administrator, or never installed, as in the case of installing a cluster smaller than the Entire Distribution.

Workaround: Ignore the message.

Cannot login if System Is Not Rebooted (4423853)

When installing in single-user mode, do not use the exit command when done. You must instead use the reboot command. If exit is used instead of reboot, the following happens:

Workaround: If the exit command is used after installing in single-user mode, reboot the system.

If the exit command is used after installing in multi-user mode and no root users remain logged in, reboot the system.