Chapter 4 End-of-Software Support Statements

This chapter lists end-of-support statements. No new end-of-software support statements have been added since this document was published on the Solaris 8 10/00Documentation CD and in the Installation Kiosk on the Solaris 8 10/00 Installation CD.

Current Release

HotJava Browser

The HotJava^TM browser is no longer supported.

Solaris Java Development Kit: JNI 1.0 Interface

The 1.0 version of the Java Native Interface (JNI 1.0) is no longer supported by the Solaris Java Development Kit version 1.2 (JDK^TM 1.2).

Support in the Solaris Java Development Kit (JDK) for the 1.0 version of the Java Native Interface (JNI 1.0) has been removed. JNI 1.0 is also known as the Native Method Interface (NMI).

Solstice AdminSuite 2.3/AutoClient 2.1

Solstice AdminSuite^TM 2.3 software is no longer supported with the Solaris 8 operating environment. Any attempt to run Solstice AdminSuite 2.3 to configure a Solstice AutoClient or diskless client will result in a failure for which no patch is available or planned. While it may be possible to manually edit configuration files to enable diskless clients, such an operation is not recommended or supported.

F3 Font Technology

F3 fonts and the TypeScaler rasterizer, Sun's proprietary scalable font technology, is no longer supported. Sun will continue to support the industry standard font formats, Type1 and TrueType.

XGL

XGL is no longer supported.

Derived Type paddr_t

The paddr_t data type found in sys/types.h is not supported in the 64-bit compilation environment. It is currently only available in the 32-bit compilation environment.

Changes to Application Programming Interfaces (APIs) for User Accounting Data

Two sets of APIs allow user accounting data to be accessed by applications. The preferred set of programming interfaces for accessing and manipulating user accounting information is described on the getutxent(3C) man page. These interfaces are both more capable and more portable than the older getutent(3C) routines.

Older applications may access the underlying accounting files directly. The files /var/adm/utmp and /var/adm/wtmp and the corresponding symbolic links /etc/utmp and /etc/wtmp are no longer supported. The format of the data contained in these files constrains the future evolution of the Solaris operating environment. Applications using these files should be updated to use the documented and supported APIs.

Applications that are already using the getutent(3C) family of routines may be unaffected on small system configurations. However, in future releases these interfaces may return errors when used on very large system configurations. For this reason, use the getutxent(3C) routines for both old and new code in place of the getutent(3C) APIs.

The sysidnis(1M) System Identification Program

sysidnis(1M) is no longer supported. sysidnis(1M) is the System Identification program responsible for configuring name services during installation, upgrade, and after unconfiguration using sys-unconfig(1M).

sysidnis(1M) has been replaced by sysidns(1M).

Sun4c-Based Systems

The following Sun4c--based architecture systems and servers based on these systems are no longer supported.

• SPARCstation^TM SLC

• SPARCstation ELC

• SPARCstation IPC

• SPARCstation IPX

• SPARCstation 1

• SPARCstation 1+

• SPARCstation 2

All hardware options (such as SCSI devices) and supported configurations that are dependent on the Sun4c-based architecture are no longer supported.

SPARCstation Voyager

SPARCstation Voyager^TM systems are no longer supported.

SPARC Xterminal 1

SPARC Xterminal 1^TM systems are no longer supported.

Future Releases

GMT Zoneinfo Timezones

The zoneinfo timezones in the following left column may no longer be supported in a future release. These files may be removed from /usr/share/lib/zoneinfo. Replace usage of the zoneinfo timezones in the left column with the equivalent timezones in the right column.

When setting the TZ environment variable to a zoneinfo GMT[+-]* timezone, the timezone must be preceded with a colon (':') character. For example, replace the zoneinfo timezone setting TZ=:GMT+1, which is 1 hour east of the Prime Meridian, with the equivalent zoneinfo timezone setting TZ=:Etc/GMT-1.

The planned removal of the zoneinfo GMT[+-]* timezones does not affect POSIX-style GMT[+-]* timezone settings, for example TZ=GMT+1 (without the colon character). An equivalent zoneinfo timezone, located under /usr/share/lib/zoneinfo/Etc and with the same name, may be used instead. The POSIX-style timezone only displays the string "GMT" in the abbreviated timezone name, while the zoneinfo timezone displays the offset from GMT. For example, replace the POSIX-style timezone setting, TZ=GMT+1, with the equivalent zoneinfo timezone setting TZ=:Etc/GMT+1.

See environ.5 and zoneinfo.4 for more information.

Solstice AdminTool

Solstice AdminTool (admintool) may no longer be supported in a future release. This tool performs user management, printer management, software package management, serial port management, group management, and host management.

The print management function is currently available in the Solaris 8 operating environment (see /usr/sadm/admin/bin/printmgr).

Solstice Enterprise Agents

Solstice Enterprise Agents may no longer be supported in a future release. This functionality has been replaced by the Solaris Web-Based Enterprise Management (WBEM) Services feature that is released as part of the Solaris 8 operating environment.

XIL

XIL may no longer be supported in a future release. An application using 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 8.
     Please notify your application supplier. 
     The message can be suppressed by setting the environment variable
     "_XIL_SUPPRESS_OBSOLETE_MSG.

Lightweight Directory Access Protocol (LDAP) Client Library

LDAP client library, libldap.so.3, may no longer be supported in a future release. The new version of this library, libldap.so.4, is compliant with the draft-ietf-ldapext-ldap-c-api-04.txt revision of the ldap-c-api draft from the Internet Engineering Task Force (IETF).

JDK 1.1.x and JRE 1.1.x

Version 1.1.x of the JDK and JRE may no longer be supported in a future release. Near-equivalent functionality is supported by Java 2 Standard Edition, versions 1.2 onwards.

SUNWrdm

The SUNWrdm package, formerly containing release notes and installed in /usr/share/release_info, may not be included on the Solaris Software CD in a future release.

For release notes, refer to the Release Notes on the Solaris Documentation CD, the printed Installation Release Notes, or the Release Notes Update available on http://docs.sun.com.

crash(1M) Utility

The crash(1M) utility may no longer be supported in a future release. The crash command is a utility that examines system crash dump files, whose functionality is superseded by the new mdb(1) utility. 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 wish to transition from using crash to using mdb.

Kerberos Version 4 Client

The Kerberos version 4 client may be removed in a future release. This 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, in the kerberos(3KRB) library, and in the ONC RPC programming API kerberos_rpc(3KRB).

adb(1) Map Modifiers and Watchpoint Syntax

The adb(1) utility may be implemented as a link to the new mdb(1) utility in a future version of the Solaris 8 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. They are:

• The text output format of some subcommands is different in mdb(1). Macro files are formatted using the same rules, but scripts that depend on the output of other subcommands may need to be modified.

• The watchpoint length specifier syntax in mdb(1) is different from the syntax described in adb(1). The adb(1) watchpoint commands :w, :a, and :p allow an integer length (in bytes) to be inserted between the colon and the command character. In mdb(1), the count should be specified following 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).

OpenWindows Toolkits for Developers

OpenWindows^TM XView^TM and OLIT toolkits may no longer be supported in a future release. You may want to migrate to the Motif toolkit. To disable the warning message, use #define OWTOOLKIT_WARNING_DISABLED or -D.

OpenWindows Environment For Users

The OpenWindows environment may no longer be supported in a future release. You may want to migrate to CDE, the Common Desktop Environment.

Federated Naming Service (FNS)/XFN Libraries and Commands

The Federated Naming Service based on the X/Open XFN standard may no longer be supported in a future release.

Solaris ipcs(1) Command

The ability to apply the ipcs(1) command to system crash dumps using the -C and -N command line options may no longer be supported in a future release. Equivalent functionality is now provided by the mdb(1) ::ipcs debugger command.

Deprecate sendmail -AutoRebuildAliases Option

The -AutoRebuildAliases option for the sendmail(1m) man page is deprecated and may no longer be supported in a future release.

sun4d-Based Servers

The following sun4d-based architecture servers may no longer be supported in a future release.

• SPARCserver^TM 1000

• SPARCcenter^TM 2000