test

Solaris 9 (SPARC Platform Edition) 9/02 Release Notes

Installation Bugs That Occur During an Upgrade

Live Upgrade Does Not Update /etc/group File on Boot Environment When Installing Solaris Flash Archive (4683186)

If you use Solaris Live Upgrade to install a Solaris Flash archive on a boot environment, the /etc/group file is not correct. The archive contains the /etc/group file that was archived and does not reflect the /etc/group file from the currently running boot environment. The /etc/group file on the boot environment must be identical to the file on the currently running system.

Workaround: After you install a Solaris Flash archive on a boot environment, you must copy the /etc/group file from the currently running system to the new boot environment. Follow these steps.

  1. Become superuser.

  2. Mount the boot environment that you want to patch


    # lumount boot-envir-name mount-point

    In the previous command, boot-envir-name is the name of the boot environment whose file systems you want to mount. mount-point is the mount point of the file system.

  3. Copy the /etc/group file from the currently running system to the new boot environment.


    # cp /etc/group mount-point/etc/group

  4. Unmount the new boot environment. 


    # luumount boot-envir-name

luupgrade Command Cannot Add Patches When a Patch List File Is Specified (4679511)

If you use the -s option with the luupgrade command to add patches with a directory and a patch list file, the patches are not added. A message similar to the following message is displayed:


/usr/sbin/luupgrade [52]:		3 patch-list-file: bad number

In the previous message, patch-list-file is the patch list file you specified for the luupgrade command to use to add patches.

Workaround: To add patches specifying a patch list file, perform the following steps.

  1. Become superuser.

  2. Mount the boot environment that you want to patch.


    # lumount boot-envir-name mount-point

  3. Add the patches to the boot environment.


    # /usr/sbin/patchadd -R mount-point -M  patch-path patch-list-file-name

    In the previous command, patch-path is the path name of a directory that contains patches to add. The patch-list-file-name is the file that contains the list of patches you want to add.

  4. Unmount the boot environment. 


    # luumount boot-envir-name

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 9/02 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 From Solaris 8 Operating Environment Might Create Redundant Kerberos Privacy Mechanisms (4672740)

In the Solaris 9 9/02 operating environment, the Kerberos version 5 global mechanism includes privacy support. Therefore, the Kerberos domestic mechanism is not needed. If you installed the Kerberos domestic mechanism that is located in /usr/lib/gss/do/mech_krb.so.1 on a Solaris 8 system, remove the Kerberos domestic mechanism before you upgrade the system to the Solaris 9 9/02 operating environment.

Workaround: Follow these steps before you upgrade to the Solaris 9 9/02 operating environment.

  1. Type the following command to determine if the Kerberos domestic mechanism is installed on the system.


    % pkginfo | fgrep ' SUNWk5'

    • If the output of this command includes any SUNWk5 package names, the Kerberos domestic mechanism is installed on the system. Go to step 2.

    • If the output does not include any SUNWk5 package names, the Kerberos domestic mechanism is not installed on the system. Skip the rest of these steps. Upgrade the system.

  2. Back up the /etc/nfssec.conf and /etc/gss/qop files by typing the following command.


    % tar -cf /var/tmp/krb_config_files.tar /etc/nfssec.conf /etc/gss/qop

  3. Verify that the files are backed up by typing the following command.


    % tar -tf /var/tmp/krb_config_files.tar

  4. Remove each package that is listed in the output of step 1.


    % pkgrm package-name package-name package-name

  5. Upgrade to the Solaris 9 9/02 operating environment.

    The upgrade program updates the global Kerberos mechanism code and enables Kerberos privacy support.

  6. In a text editor, change the following lines in the /etc/gss/mech file.

    • Uncomment the following line.


      kerberos_v5     1.2.840.113554.1.2.2    gl/mech_krb5.so gl_kmech_krb5

      If necessary, add the previous line to the /etc/gss/mech file.

    • Remove the following line.


      kerberos_v5     1.2.840.113554.1.2.2    do/mech_krb5.so do_kmech_krb5

    • Restore the /etc/nfssec.conf and /etc/gss/qop files by typing the following command.


      % tar -xf /var/tmp/krb_config_files.tar

preremove Scripts in Solaris 9 and Solaris 9 9/02 Asian Language Packages Do Not Execute Properly During Upgrade (4707449)

The preremove scripts included in the Asian language packages of the Solaris 9 and Solaris 9 9/02 software do not execute properly during an upgrade with Disk Space Reallocation (DSR). If you attempt to upgrade to a newer release of the Solaris operating environment, the following error message is displayed in the /var/sadm/system/logs/update_log file.


Removing package SUNWkwbcp:
/a/var/sadm/pkg/SUNWkwbcp/install/preremove: /a/usr/4lib: does not exist
pkgrm: ERROR: preremove script did not complete successfully

Removal of SUNWkwbcp failed.
pkgrm return code = 1
Removing package SUNWkbcp:
/a/var/sadm/pkg/SUNWkbcp/install/preremove: /a/usr/4lib: does not exist
pkgrm: ERROR: preremove script did not complete successfully
Removal of SUNWkbcp failed.
pkgrm return code = 1
Removing package SUNWcwbcp:
/a/var/sadm/pkg/SUNWcwbcp/install/preremove: /a/usr/4lib: does not exist
pkgrm: ERROR: preremove script did not complete successfully

Removal of SUNWcwbcp failed.
pkgrm return code = 1
Removing package SUNWcbcp:
/a/var/sadm/pkg/SUNWcbcp/install/preremove: /a/usr/4lib: does not exist
pkgrm: ERROR: preremove script did not complete successfully

Removal of SUNWcbcp failed.
pkgrm return code = 1
Removing package SUNWhwbcp:
/a/var/sadm/pkg/SUNWhwbcp/install/preremove: /a/usr/4lib: does not exist
pkgrm: ERROR: preremove script did not complete successfully

Removal of SUNWhwbcp failed.
pkgrm return code = 1
Removing package SUNWhbcp:
/a/var/sadm/pkg/SUNWhbcp/install/preremove: /a/usr/4lib: does not exist
pkgrm: ERROR: preremove script did not complete successfully

Removal of SUNWhbcp failed.
pkgrm return code = 1

Workaround: Ignore the error message.

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

If you upgrade to the Solaris 9 9/02 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 9/02 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 9/02 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 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 9/02 operating environment. For specific instructions, see the System Administration Guide: Basic Administration.

If you attempt to install the Solaris 9 9/02 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.

Upgrading the JavaSpaces Data Store to Prevent WBEM Data Loss (4365035)

If you upgrade from the Solaris 8 (Solaris WBEM Services 2.0), or the Solaris 8 6/00 (WBEM Services 2.1), operating environments to the Solaris 9 9/02 (Solaris WBEM Services 2.5) operating environment, your existing data is lost.

Workaround: Recompile the proprietary Managed Object Format (MOF) files after you perform an upgrade.