test

Solaris 9 8/03 Release Notes

Installation Bugs That Occur During an Upgrade

Problem With the luupgrade Commmand When Installing a Solaris Flash Differential Archive (4890708)

If you have created a new boot environment with Solaris Live Upgrade, you cannot install a Solaris Flash differential archive on the new boot environment by using the luupgrade command. The following error message is displayed:


/usr/sbin/luupgrade[607]: ludo:  not found

A Solaris Flash differential archive is a minor update to the operating environment on a boot environment that has been upgraded with a Solaris Flash archive.

Workaround: To enable the use of the luupgrade command to install a differential archive, edit the /etc/default/lu file. Change the existing PATH variable setting so that /etc/lib/lu is the first component in the path.

Do not use this path:


PATH=/etc:/sbin:/usr/bin:/usr/sbin:$PATH

Change the path to the following:


PATH=/etc/lib/lu:/etc:/sbin:/usr/bin:/usr/sbin:$PATH

For more information, see the Solaris 9 Installation Guide.

Upgrade Fails to Install SUNWceudt Package (4826785)

If you upgrade from the Solaris 9, Solaris 9 9/02, Solaris 9 12/02, or Solaris 9 4/03 operating environment to the Solaris 9 8/03 release, the following errors occur when you use the pkgchk command with the -n option:


ERROR: /usr/dt/appconfig/types/cs_CZ.ISO8859-2/datatypes.dt
pathname does not exist
ERROR: /usr/dt/appconfig/types/cs_CZ.ISO8859-2/develop.dt
pathname does not exist
ERROR: /usr/dt/appconfig/types/cs_CZ.ISO8859-2/dtfile.dt
pathname does not exist
ERROR: /usr/dt/appconfig/types/cs_CZ.ISO8859-2/dtmail.dt
pathname does not exist
ERROR: /usr/dt/appconfig/types/cs_CZ.ISO8859-2/dtpad.dt
pathname does not exist
ERROR: /usr/dt/appconfig/types/cs_CZ.ISO8859-2/print.dt
pathname does not exist
ERROR: /usr/dt/appconfig/types/cs_CZ.ISO8859-2/uxstd.dt
pathname does not exist

Workaround: Use the Solaris 9 8/03 DVD or the Solaris 9 8/03 Software 1 of 2 CD to add back the SUNWceudt package. Follow these steps:

  1. Become superuser.

  2. Remove the SUNWceudt package.


    # pkgrm SUNWceudt

  3. Change directories to the product directory.


    # cd path-to-Solaris-9/Product

  4. Add the SUNWceudt package.


    # pkgadd -d `pwd` SUNWceudt

Installer Text Display Problem When Using Solaris Live Upgrade (4736488)

When using the Solaris Live Upgrade luupgrade(1M) command with the -i option to complete an upgrade of an inactive boot environment, the text that the installers display might be unreadable in some languages. The text is corrupted when the installers request fonts that do not exist on the older release that is on the current boot environment.

Workaround: Choose one of the following workarounds:

SPARC: Removal of SUNWjxcft Package Records Error During Upgrade (4525236)

When you upgrade from the Solaris 8 operating environment to the Solaris 9 or the Solaris 9 8/03 operating environment, a problem is encountered when the SUNWjxcft package is removed. The following error message is recorded in the upgrade_log file:


Removing package SUNWjxcft:
Can't open /a/usr/openwin/lib/locale/ja/X11/fonts/TTbitmaps/fonts.upr
Can't open /a/usr/openwin/lib/locale/ja/X11/fonts/TTbitmaps/fonts.scale
Can't open /a/usr/openwin/lib/locale/ja/X11/fonts/TTbitmaps/fonts.alias
Can't open /a/usr/openwin/lib/locale/ja/X11/fonts/TT/fonts.upr
Can't open /a/usr/openwin/lib/locale/ja/X11/fonts/TT/fonts.scale
Can't open /a/usr/openwin/lib/locale/ja/X11/fonts/TT/fonts.alias
Removal of <SUNWjxcft> was successful

Workaround: Ignore the error message.

Upgrading to Solaris 9 8/03 Operating Environment Might Disable Existing Secure Shell Daemon (sshd) (4626093)

If you upgrade to the Solaris 9 8/03 operating environment on a system that is running a third-party Secure Shell, such as OpenSSH, from the /etc/init.d/sshd daemon, the upgrade disables the existing Secure Shell daemon. During an upgrade, the Solaris 9 8/03 upgrade software overwrites the contents of /etc/init.d/sshd.

Workaround: Choose one of the following workarounds:

Upgrade Fails if /export Is Near Capacity (4409601)

If the /export directory is near full capacity and you upgrade to the Solaris 9 8/03 operating environment, space requirements for /export are miscalculated. The upgrade then fails. This problem commonly occurs if a diskless client is installed, or if third-party software is installed in the /export directory. The following message is displayed:


WARNING: Insufficient space for the upgrade.

Workaround: Before you upgrade, choose one of the following workarounds:

Upgrading Diskless Client Servers and Clients (4363078)

If your system currently supports diskless clients that were installed with the Solstice AdminSuiteTM 2.3 Diskless Client tool, you must perform two steps. First, delete all existing diskless clients that are the same Solaris version and architecture as the server. Then, install or upgrade to the Solaris 9 8/03 operating environment. For specific instructions, see the System Administration Guide: Basic Administration.

If you attempt to install the Solaris 9 8/03 operating environment over existing diskless clients, the following error message might be displayed:


The Solaris Version (Solaris version-number) on slice <xxxxxxxx> cannot 
be upgraded. 
There is an unknown problem with the software configuration installed 
on this disk.

In this error message, version-number refers to the Solaris version that is currently running on your system. <xxxxxxxx> refers to the slice that is running this version of the Solaris operating environment.