This chapter lists end-of-support statements.
The following end-of-software support statements have been added since this document was published on the Solaris 9 Documentation CD and in the Installation Kiosk on the Solaris 9 Installation CD.
The adb(1) utility is implemented as a link to the new mdb(1) utility in this release of the Solaris operating environment.
The mdb(1) man page describes the features of the new debugger, including its adb(1) compatibility mode. Even in this compatibility mode, differences between adb(1) and mdb(1) exist. These differences include the following:
The text output format of some subcommands is different in mdb(1). Macro files are formatted by using the same rules, but scripts that depend on the output of other subcommands might need to be modified.
The watchpoint-length specifier syntax in mdb(1) is different from the syntax that is described in adb(1). The adb(1) watchpoint commands :w, :a, and :p enable an integer length (in bytes) to be inserted between the colon and the command character. In mdb(1), the count should be specified after the initial address as a repeat count.
The adb(1) command 123:456w is specified in mdb(1) as 123,456:w.
The /m, /*m, ?m, and ?*m format specifiers are not recognized or supported by mdb(1).
The AnswerBook2TM server is no longer included in this release. Existing AnswerBook2 servers can run on the Solaris 9 operating environment. Solaris documentation is available on the Solaris Documentation CD in online formats. All Solaris documentation is also always available at http://docs.sun.com.
The aspppd(1M) utility is no longer included in this release. Use the pppd(1M) utility with Solaris PPP 4.0 that is included in the Solaris 9 operating environment.
The ATOK8 Japanese input method is no longer supported in this release. The ATOK12 Japanese input method that is included in the Solaris 9 operating environment provides functionality similar to ATOK8, with several enhancements.
The crash(1M) utility is no longer supported in this release. In the Solaris 9 operating environment, the mdb(1) utility provides similar functionality to the crash command by examining system crash dump files. The crash command's interface has been structured around implementation details, such as slots, that have no relation to the Solaris operating system implementation.
"Transition From crash" in Solaris Modular Debugger Guide provides information for users who are making the transition from using crash to using mdb.
The capability of applying the ipcs(1) command to system crash dumps by using the -C and -N command-line options is no longer supported in this release. Equivalent functionality is now provided by the mdb(1) ::ipcs debugger command.
The cs00 Japanese input method is no longer supported in the Solaris 9 operating environment. Related interfaces, such as the xci interface, the Japanese Feature Package (JFP) libmle API, and the mle command, are also no longer supported in the Solaris 9 operating environment.
If you upgrade to the Solaris 9 operating environment from a previous release, the existing public user dictionary /var/mle/ja/cs00/cs00_u.dic will be removed.
Two Japanese input methods, ATOK12 and Wnn6, are supported in the Solaris 9 operating environment. For more information on these input methods, see International Language Environments Guide.
The name of the EA directory has been changed to ExtraValue in the Solaris 9 operating environment.
The MD21 disk controller for ESDI drives is no longer supported in the Solaris 9 operating environment.
The enable_mixed_bcp tunable is no longer supported in this release. In Solaris releases prior to the Solaris 9 operating environment, the /etc/system variable enable_mixed_bcp could be set to 0 to disable dynamic linking of partially statically linked SunOSTM 4.0 and compatible executables. The system used dynamic linking for these executables by default. In the Solaris 9 operating environment, dynamic linking is always used for these executables, and the enable_mixed_bcp tunable has been removed from the system. This change does not affect binary compatibility for SunOS 4.0 and compatible executables in any way.
The japanese locale name alternate of the ja Japanese Extended UNIX® Code (EUC) locale is no longer supported in this release. This locale name facilitated migration from the Solaris 1.0 release, and compatible releases. You can use ja or ja_JP.eucJP as the Japanese EUC locale with the Solaris 9 operating environment. The Solaris 1.0 BCP (JLE) application, and compatible versions, can still run in the Solaris 9 operating environment without any changes.
Version 1.2.2 of the JavaTM SDK (SUNWj2dev) is no longer included in the Solaris 9 release. Near-equivalent functionality is supported by Java 2 Standard Edition, versions 1.4 and compatible versions. Current and previous versions of JDK and JRE are available for download from http://java.sun.com.
Version 1.1.8 of the JDK and version 1.1.8 of the JRE are no longer supported in this release. Near-equivalent functionality is supported by Java 2 Standard Edition, versions 1.4 and compatible versions. Current and previous versions of JDK and JRE are available for download from http://java.sun.com.
Development in the OpenWindowsTM XViewTM and OLIT toolkits is no longer supported in this release and developers are encouraged to migrate to the Motif toolkit. Applications that were developed with the OpenWindows XView and OLIT toolkits can still run on the Solaris 9 operating environment.
The OpenWindows environment is no longer supported in this release. The Common Desktop Environment (CDE) is the default desktop environment that is included in the Solaris 9 operating environment. Applications that use the OpenWindows XView and OLIT toolkits can still run on the Solaris 9 operating environment in CDE.
The priority_paging and cachefree tunable parameters are not supported in the Solaris 9 release. These parameters have been replaced with an enhanced file system caching architecture that implements paging policies similar to priority paging, but always enabled. Attempts to set these parameters in the /etc/system file result in boot-time warnings such as the following:
sorry, variable 'priority_paging' is not defined in the 'kernel' sorry, variable 'cachefree' is not defined in the 'kernel' |
If you upgrade to the Solaris 9 release or pkgadd the SUNWcsr packages and your /etc/system file includes the priority_paging or cachefree parameters, the following occurs:
The following message is displayed if the priority_paging or cachefree parameters are set in the /etc/system file:
NOTE: /etc/system has been modified since it contains references to priority paging tunables. Please review the changed file. |
Comments are inserted in the /etc/system file before any line that sets priority_paging or cachefree. For example, if priority_paging is set to 1, this line is replaced with the following lines:
* NOTE: As of Solaris 9, priority paging is unnecessary and * has been removed. Since references to priority paging-related tunables * will now result in boot-time warnings, the assignment below has been * commented out. For more details, see the Solaris 9 Release Notes, or * the "Solaris Tunable Parameters Reference Manual". * set priority_paging=1 |
The s5fs file system is no longer supported in this release. The s5fs file system supports the installation of Interactive UNIX applications which is no longer required in the Solaris operating environment.
Some features of the sendmail utility are no longer supported in this release. The affected features are modifications that are mostly nonstandard and specific to Sun. These features include special syntax and semantics for V1/Sun configuration files, the remote mode feature, the AutoRebuildAliases option, and the three sun-reverse-alias features.
More information about these features and migration issues is located at http://www.sendmail.org/vendor/sun/solaris9.html.
The SUNWebnfs package is no longer included on the Solaris operating environment media.
The library and documentation are available for download from http://www.sun.com/webnfs.
The following servers that are based on the sun4d architecture are no longer supported in this release.
SPARCserverTM 1000
SPARCcenterTM 2000
The SUNWrdm package, which formerly contained text release notes, is no longer included on the Solaris Software CD in this release.
For release notes, refer to the Release Notes on the Solaris Documentation CD, the printed Installation Release Notes, or the most current release notes available on http://docs.sun.com.
AdminTool (admintool), including swmtool, might not be supported in a future release.
Asian short locale names, including zh, zh.GBK, zh.UTF-8, ko, ko.UTF-8, and zh_TW, might not be listed in the dtlogin language list in a future release. The Solaris 8 and Solaris 9 releases provide new ISO standard locale names, including zh_CN.EUC, zh_CN.GBK, zh_CN.UTF-8, ko_KR.EUC, ko_KR.UTF-8, and zh_TW.EUC.
The Device Management entries in power.conf(4) might not be supported in a future release. Similar functionality is provided by the Automatic Device Power Management entries in the Solaris 9 operating environment.
The Federated Naming Service that is based on the X/Open XFN standard might not be supported in a future release.
The /usr/share/lib/zoneinfo/GMT[+-]* time zones might not be supported in a future release. These files might be removed from /usr/share/lib/zoneinfo. Replace usage of the zoneinfo time zones with the equivalent Etc/GMT[-+]* file. See the man pages zoneinfo(4) and environ(5) for more information.
Version 1.2.2 of the JRE might not be supported in a future release. Near-equivalent functionality is supported by Java 2 Standard Edition, versions 1.4 and compatible versions. Current and previous versions of JRE are available for download from http://java.sun.com.
The Kerberos version 4 client might be removed from a future release. This client includes the Kerberos version 4 support in the kinit(1), kdestroy(1), klist(1), ksrvtgt(1), mount_nfs(1M), share(1M), and kerbd(1M) commands. The Kerberos version 4 client also includes support in the kerberos(3KRB) library, and in the ONC RPC programming API kerberos_rpc(3KRB).
Korean CID fonts might not be supported in a future release. You can use the Korean TrueType fonts that are included in the Solaris operating environment as a replacement for Korean CID fonts.
LDAP client library, libldap.so.3, might not be included in a future release. The current version of this library, libldap.so.5, is compliant with the draft-ietf-ldapext-ldap-c-api-05.txt revision of the ldap-c-api draft from the Internet Engineering Task Force (IETF).
NIS+ might not be supported in a future release. Tools to aid the migration from NIS+ to LDAP are available in the Solaris 9 operating environment. For more information, visit http://www.sun.com/directory/nisplus/transition.html.
The pam_unix(5) module might not be supported in a future release. Similar functionality is provided by pam_authtok_check(5), pam_authtok_get(5), pam_authtok_store(5), pam_dhkeys(5), pam_passwd_auth(5), pam_unix_account(5), pam_unix_auth(5), and pam_unix_session(5).
Perl version 5.005_03 might not be supported in a future release. In the Solaris 9 operating environment, the default version of Perl has been changed to a version that is not binary compatible with the earlier version (5.005_03), although the earlier version is still retained for compatibility. Customer-installed modules need to be rebuilt and reinstalled against the new version. Modify any scripts that require the use of version 5.005_03 to explicitly use the 5.005_03 version of the interpreter (/usr/perl5/5.005_03/bin/perl) instead of the default version (/bin/perl, /usr/bin/perl, or /usr/perl5/bin/perl).
The following power management I/O control commands (ioctls) might not be supported in a future release.
PM_DISABLE_AUTOPM
PM_REENABLE_AUTOPM
PM_SET_CUR_PWR
PM_GET_CUR_PWR
PM_GET_NORM_PWR
The following alternative ioctls are supported in the Solaris 9 operating environment.
PM_DIRECT_PM
PM_RELEASE_DIRECT_PM
PM_GET_CURRENT_POWER
PM_SET_CURRENT_POWER
PM_GET_FULL_POWER
For more information on these alternative ioctls, see the pm(7D) man page.
Solaris Volume Manager's Transactional Volumes (trans metadevices) might not be supported in a future release to reduce redundancy on the Solaris feature set. Similar functionality is provided by UFS Logging, included in the Solaris 8 operating environment, and compatible versions.
Solstice Enterprise Agents might not be supported in a future release.
The SPC driver might not be supported in a future release.
sun4m hardware might not be supported in a future release of the Solaris operating environment.
XIL might not be supported in a future release. An application that uses XIL causes the following warning message to be displayed.
WARNING: XIL OBSOLESCENCE This application uses the Solaris XIL interface which has been declared obsolete and may not be present in version of Solaris beyond Solaris 9. Please notify your application supplier. The message can be suppressed by setting the environment variable "_XIL_SUPPRESS_OBSOLETE_MSG. |
The xutops print filter might not be supported in a future release. Similar functionality is provided by the mp(1) print filter in the Solaris 9 operating environment.