Technical data

Solaris Trusted Extensions Upgrade Issues (6616585)
When you upgrade Solaris Trusted Extensions from the Solaris 10 11/06 or Solaris 10 8/07
release to the current Solaris 10 5/08 release, unwanted localized Solaris Trusted Extensions
packages are installed on your system. This bug occurs because the Solaris Trusted Extensions
installer in the Solaris 10 11/06 or Solaris 10 8/07 releases installs localized packages by default.
No error message is displayed.
Workaround: Before upgrading Solaris Trusted Extensions to the current release, remove the
following localized Solaris Trusted Extensions packages:
SUNWjdtts SUNWkdtts
SUNWjmgts SUNWkmgts
SUNWjtsman SUNWktsu
SUNWjtsu SUNWodtts
SUNWtgnome-l10n-doc-ja SUNWtgnome-l10n-ui-ko
SUNWtgnome-l10n-ui-it SUNWtgnome-l10n-ui-zhHK
SUNWtgnome-l10n-ui-sv SUNWtgnome-l10n-ui-es
SUNWtgnome-l10n-doc-ko SUNWtgnome-l10n-ui-ptBR
SUNWtgnome-l10n-ui-ja SUNWtgnome-l10n-ui-zhTW
SUNWtgnome-l10n-ui-zhCN SUNWtgnome-l10n-ui-fr
SUNWtgnome-l10n-ui-de SUNWtgnome-l10n-ui-ru
System Cannot CommunicateWith ypbind After
Upgrade (6488549)
This bug occurs during an upgrade from Solaris 10 Hardware 2 release to the current Solaris 10
5/08 release.
In the Solaris 10 Hardware 2 release, the name_service.xml le for any name service, such as
NIS, NIS+, FILES, or LDAP is as follows:
# ls -l name_service.xml
lrwxrwxrwx 1 root root 10 Apr 10 16:26 name_service.xml -> ns_files.xml
If the name service is NIS, the name_service.xml le links to ns_files.xml. However, the
contents of the ns_files.xml are the same as ns_nis.xml.
Upgrade Issues and Bugs
Chapter 1 • Installation Issues 41