test

Solaris 9 8/03 Release Notes

Chapter 3 End-of-Software Support Statements

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 8/03 Documentation CD and in the Installation Kiosk on the Solaris 9 8/03 Installation CD.

Features Removed From the Solaris 9 Operating Environment

adb Map Modifiers and Watchpoint Syntax

The adb utility is implemented as a link to the new mdb utility in this release of the Solaris operating environment.

The mdb(1) man page describes the features of the new debugger, including its adb compatibility mode. Even in this compatibility mode, differences between adb(1) and mdb exist. These differences include the following:

AnswerBook2 Server

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.

aspppd Utility

The aspppd utility is no longer included in this release. Instead, use the pppd(1M) utility with Solaris PPP 4.0 utility that is included in the Solaris 9 operating environment.

ATOK8 Japanese Input Method

The ATOK8 Japanese input method is no longer supported in this release. The ATOK12 Japanese input method is included in the Solaris 9 operating environment. The ATOK12 Japanese input method provides functionality that is similar to the ATOK8, with the addition of several enhancements.

crash Utility

The crash utility is no longer supported in this release. In the Solaris 9 operating environment, the mdb(1) utility provides a function that is similar to the crash utility. The mdb utility also examines system crash dump files. The crash utility's interface has been structured around implementation details, such as slots, that have no relation to the Solaris operating system implementation.

“Transition From” in Solaris Modular Debugger Guide provides information for users who are making the transition from using crash to using mdb.

Crash Dump Options for Solaris ipcs Command

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 capability is now provided by the mdb(1) ::ipcs debugger command.

cs00 Japanese Input Method

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 is removed.

Two Japanese input methods, ATOK12 and Wnn6, are supported in the Solaris 9 operating environment. For more information on the ATOK12 and Wnn6 input methods, see the International Language Environments Guide.

x86: devconfig Command

The devconfig command is no longer supported in this release.

x86: Device and Driver Software Support

The following table lists devices and driver software that are no longer supported in this release:

Table 3–1 Devices and Driver Software

Name of Physical Device 

Name of Driver 

Type of Card 

Mylex/Buslogic FlashPoint Ultra PCI SCSI 

flashpt

SCSI HBA 

Madge Token Ring Smart 16/4, Madge Token Ring Smart 16/4 PCI BM Mk2, Madge Token Ring Smart 16/4 PCI BM Mk1, and Madge Token Ring PCI Presto 

mtok

Network 

Compaq Integrated NetFlex-3 10/100 T PCI, Compaq NetFlex-3/P, Compaq NetFlex-3 DualPort 10/100 TX PCI, Compaq Netelligent 10 T PCI, and Compaq Netelligent 10/100 TX PCI 

cnft

Network 

Early Access (EA) Directory

The name of the EA directory has been changed to ExtraValue in the Solaris 9 operating environment.

Emulex MD21 Disk Controller for ESDI Drives

The MD21 disk controller for ESDI drives is no longer supported in the Solaris 9 operating environment.

enable_mixed_bcp Tunable

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.

x86: Intel 486–Based Systems

The Solaris operating environment is no longer supported on Intel 486–based systems.

japanese Locale Name Alternate

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.

Java Software Developer's Kit (SDK) 1.2.2

Version 1.2.2 of the JavaTM SDK (SUNWj2dev) is no longer included in the Solaris 9 release. Near-equivalent capability is supported by Java 2 Standard Edition, versions 1.4 and compatible versions. Current and previous versions of JDK and Java runtime environment (JRE) are available for download from http://java.sun.com.

JDK 1.1.8 and JRE 1.1.8

Version 1.1.8 of the JDK and version 1.1.8 of the JRE are no longer supported in this release. Near-equivalent capability 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.

Kerberos Version 4 Client

The Kerberos version 4 client was removed from the Solaris 8 operating environment. This client includes the Kerberos version 4 support in the kdestroy, kerbd, kinit, klist, ksrvtgt, mount_nfs, and share commands. The Kerberos version 4 client also includes support in the kerberos (3KRB) library, and in the ONC RPC programming API kerberos_rpc(3KRB).

For more information, see the kdestroy(1), kinit(1), klist(1), mount_nfs(1M), and share(1M) man pages.

OpenWindows Toolkits for Developers

Development in the OpenWindowsTM XViewTM and OLIT toolkits is no longer supported in this release. 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.

OpenWindows Environment for Users

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.

Priority Paging and Related Kernel Tunables (priority_paging/cachefree)

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 that are 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:

  1. 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.

  2. 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

s5fs File System

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.

sendmail Utility Features

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 special 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.

SUNWebnfs Package

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.

sun4d–Based Servers

The following servers that are based on the sun4d architecture are no longer supported in this release:

Hardware options that are dependent on the sun4d architecture are no longer supported in this release.

SUNWrdm Package

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 that are available on http://docs.sun.com.

Features That Might Be Removed in a Future Release

device_driver Path-Name Support in add_drv System Command

The add_drv command accepts a path-name specification for the device_driver parameter. This feature might be removed in a future release of the Solaris operating environment.

In the Solaris 9 operating environment, the following warning message is written to STDERR when a path name is specified: 


Warning: pathname support will be discontinued in future releases of add_drv.

During the installation process, warning messages that are generated by the use of the path-name specification will appear in the install_log file.

For more information, see the add_drv(1M) man page.

AdminTool Command

AdminTool (admintool), including swmtool, might not be supported in a future release.

Asian Short dtlogin Names

The following Asian short locale names might not be listed in the dtlogin language list in a future release:

The Solaris 8, Solaris 9, and Solaris 9 8/03 releases provide new ISO-standard locale names, including:

asysmem() and sysmem() Interfaces

The asysmem() and sysmem() interfaces, which are exported by libadm(3lib), might not be included in a future release of the Solaris operating environment. Both interfaces are obsolete. Application developers are advised to use the sysconf(3C) library function instead.

For more information, see the sysconf(3C) man page.

Audit Daemon Interfaces

The following interfaces that are used by the Solaris audit daemon might not be supported in a future release of the Solaris operating environment:

Device Allocation Interfaces For the Basic Security Module

The following components of the device allocation mechanism of the Basic Security Module might not be included in a future release of the Solaris operating environment:

Obsolete Device Driver Interfaces (DDI)

Some device driver interfaces (DDI) might not be supported in a future release of the Solaris operating environment.

The following table lists DDI interfaces that might not be supported in a future release, along with the preferred DDI interface alternatives:

Obsolete Interface 

Preferred Interface 

mmap(9E)

devmap(9E)

identify(9E)

set to nulldev(9F)

copyin(9F)

ddi_copyin(9F)

copyout(9F)

ddi_copyout(9F)

ddi_dma_addr_setup(9F)

ddi_dma_addr_bind_handle(9F)

ddi_dma_buf_setup(9F)

ddi_dma_buf_bind_handle(9F)

ddi_dma_curwin(9F)

ddi_dma_getwin(9F)

ddi_dma_free(9F)

ddi_dma_free_handle(9F)

ddi_dma_htoc(9F)

ddi_dma_addr[buf]_bind-handle(9F)

ddi_dma_movwin(9F)

ddi_dma_getwin(9F)

ddi_dma_nextseg(9F)

ddi_dma_nextcookie(9F)

ddi_dma_nextwin(9F

ddi_dma_nextcookie(9F)

ddi_dma_segtocookie(9F)

ddi_dma_nextcookie(9F)

ddi_dma_setup(9F)

ddi_dma_*_handle(9F)

ddi_dmae_getlim(9F)

ddi_dmae_getattr(9F)

ddi_getiminor(9F)

getminor(9F)

ddi_getlongprop(9F)

ddi_prop_lookup(9F)

ddi_getlongprop_buf(9F)

ddi_prop_lookup(9F)

ddi_getprop(9F)

ddi_prop_get_int(9F)

ddi_getproplen(9F)

ddi_prop_lookup(9F)

ddi_iopb_alloc(9F)

ddi_dma_mem_alloc(9F)

ddi_iopb_free(9F)

ddi_dma_mem_free(9F)

ddi_mem_alloc(9F)

ddi_dma_mem_alloc(9F)

ddi_mem_free(9F)

ddi_dma_mem_free(9F)

ddi_map_regs(9F)

ddi_regs_map_setup(9F)

ddi_mapdev(9F)

devmap_setup(9F)

ddi_mapdev_intercept(9F)

devmap_load(9F)

ddi_mapdev_nointercept(9F)

devmap_unload(9F)

ddi_prop_create(9F)

ddi_prop_update(9F)

ddi_prop_modify(9F)

ddi_prop_update(9F)

ddi_segmap(9F)

see devmap(9E)

ddi_segmap_setup(9F)

devmap_setup(9F)

ddi_unmap_regs(9F)

ddi_regs_map_free(9F)

free_pktiopb(9F)

scsi_free_consistent_buf(9F)

get_pktiopb(9F)

scsi_alloc_consistent_buf(9F)

makecom_g0(9F)

scsi_setup_cdb(9F)

makecom_g0_s(9F)

scsi_setup_cdb(9F)

makecom_g1(9F)

scsi_setup_cdb(9F)

makecom_g5(9F)

scsi_setup_cdb(9F)

scsi_dmafree(9F)

scsi_destroy_pkt(9F)

scsi_dmaget(9F)

scsi_init_pkt(9F)

scsi_pktalloc(9F)

scsi_init_pkt(9F)

scsi_pktfree(9F)

scsi_destroy_pkt(9F)

scsi_resalloc(9F)

scsi_init_pkt(9F)

scsi_resfree(9F)

scsi_destroy_pkt(9F)

scsi_slave(9F)

scsi_probe(9F)

scsi_unslave(9F)

scsi_unprobe(9F)

ddi_peek{c,s,l,d}(9F)

ddi_peek{8,16,32,64}(9F)

ddi_poke{c,s,l,d}(9F)

ddi_poke{8,16,32,64}(9F)

in{b,w,l}(9F)

ddi_get{8,16,32}(9F)

out{b,w,l}(9F)

ddi_put{8,16,32}(9F)

repins{b,w,l}(9F)

ddi_rep_get{8,16,32}(9F)

repouts{b,w,l}(9F)

ddi_rep_put{8,16,32}(9F)

GLOBAL_DEV

Specify 0

NODEBOUND_DEV

Specify 0

NODESPECIFIC_DEV

Specify 0

ENUMERATED_DEV

Specify 0

DDI_IDENTIFIED

not needed

DDI_NOTIDENTIFIED

not needed

For more information, see the man pages section 9: DDI and DKI Driver Entry Points and the man pages section 9: DDI and DKI Kernel Functions.

Device Management Entries in power.conf

The Device Management entries in the power.conf file might not be supported in a future release. Similar capability is provided by the Automatic Device Power Management entries in the Solaris 9 operating environment.

For more information, see the power.conf(4) man page.

Device Support and Driver Software

The following table lists devices and driver software that might not be supported in a future release:

Table 3–2 Device and Driver Software

Name of Physical Device 

Name of Driver 

Type of Card 

AMI MegaRAID host bus adapter, first generation 

mega

SCSI RAID 

Compaq 53C8x5 PCI SCSI, and Compaq 53C876 PCI SCSI 

cpqncr

SCSI HBA 

Compaq SMART-2/P Array Controller and Compaq SMART-2SL Array Controller 

smartii

SCSI RAID controller 

Euro Character Input Sequences That Are Alt Key-Based and Meta Key-Based

Support might be removed from a future release for the following nonstandard-input key sequences for the Euro character in Solaris Unicode/UTF-8 locales:

Note –

In the key sequences, a hyphen indicates simultaneous keystrokes. A plus sign indicates consecutive keystrokes.

The recommended standard-input key sequences follow:

If the keyboard has no Alt Graph or Compose key, use the following key sequence:

Federated Naming Service XFN Libraries and Commands

The Federated Naming Service (FNS), which is based on the X/Open XFN standard, might not be supported in a future release.

fork() Function

The behavior of fork(), when not linked to the -lpthread library, might change in a future release of the Solaris operating environment. This behavior change makes Solaris threads consistent with Portable Operating System Interface (POSIX) threads.

The fork() function might be redefined to behave like fork1(). Therefore, fork() would replicate only the calling thread in the child process. This redefinition matches the current behavior of fork1() and of fork() when linked with -lpthread.

Support for applications that require the replicate-all behavior of fork() would still be provided.

GMT Zoneinfo Time Zones

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.

For more information, see the zoneinfo(4) and environ(5) man pages.

SPARC: Graphic Driver Support

Software support for the following graphic devices might not be provided in a future release of the Solaris operating environment:

Device 

Driver 

MG1,MG2 

bwtwo 

CG3 

cgthree 

SX/ CG14 

sx, cgfourteen 

TC 

cgeight 

TCX 

tcx 

JRE 1.2.2

Version 1.2.2 of the Java runtime environment (JRE) might not be supported in a future release. Similar capability is supported by Java 2 Standard Edition, version 1.4 and compatible versions. Current and previous versions of JRE are available for download from http://java.sun.com.

Kodak Color Management System

Support for the Kodak Color Management System (KCMSTM) might not be available in a future release of the Solaris operating environment.

Korean CID Fonts

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.

libXinput Library

The libXinput.so.0 library might not be provided in a future release of the Solaris operating environment. The libXinput.so.0 library was provided for backward compatibility with X11R4 applications that were built by using the draft standard X Input API of Solaris 2.1 and Solaris 2.2. The X11 standard X Input Extension library, libXi, was integrated in Solaris 2.3.

All applications that rely on the libXi API should be built by using the libXi shared library for future compatibility and standards conformance.

Lightweight Directory Access Protocol (LDAP) Client Library

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).

Obsolete Lightweight Process (LWP) Interfaces

The following LWP interfaces might not be supported in a future release:

These interfaces are not part of a common model with multithreading enabled by default. The interfaces have worked as expected only when used in applications that are not linked with libthread.

For more information, see the _lwp_create(2), _lwp_detach(2), _lwp_exit(2), _lwp_getprivate(2), _lwp_makecontext(2), _lwp_setprivate(2), and _lwp_wait(2) man pages.

Solaris Maintenance Updates

The separate patch collections provided in conjunction with the Solaris releases, the Solaris Maintenance Updates (MUs), might not be made available at future releases.

Nameless Interface Groups Feature

The Nameless Interface Groups feature, enabled by ndd /dev/ip ip_enable_group_ifs, might not be supported in a future release. Use the supported IP Network Multipathing feature, which provides similar capability. IP multipathing groups can be formed by using the group keyword of the ifconfig command.

For more information, see the ndd(1M) and ifconfig(1M) man pages.

Netscape 4.7x

NetscapeTM 4.7x software might not be supported in a future release of the Solaris operating environment.

Netscape 6.2x and Netscape 7.0

Netscape 6.2x software and Netscape 7.0 software might not be supported in a future release of the Solaris operating environment.

netstat -k Option

The unsupported -k option of netstat, which reports on all named kstats on the running OS instance, might be removed in a future release. Use the supported kstat command, which provides similar capability. The kstat command was introduced in the Solaris 8 operating environment.

For more information, see the kstat(1M) man page.

NIS+ Name Service Type

Network Information Service Plus (NIS+) might not be supported in a future release. Tools to aid in 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.

pam_unix Module

The pam_unix module might not be supported in a future release. Similar capability is provided by pam_authtok_check, pam_authtok_get, pam_authtok_store, pam_dhkeys, pam_passwd_auth, pam_unix_account, pam_unix_auth, and pam_unix_session.

For more information, see the pam_unix(5), 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

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). However, the earlier version of Perl 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).

Power Management I/O Control Commands

The following power management I/O control (ioctls) commands might not be supported in a future release:

The following alternative ioctls are supported in the Solaris 9 8/03 operating environment:

For more information on these alternative ioctls, see the ioctl(2) man page.

64-bit SPARC: ptrace Interface in libc

The 64-bit version of the ptrace interface that is included in libc might not be supported in a future release. The proc interface replaces this functionality.

For more information, see the proc(4) man page.

sendmailvars and the L and G sendmail.cf commands

The sendmailvars database that is listed in nsswitch.conf(4) might not be supported in a future release. This feature could not be enabled without using the L or G sendmail.cf commands. This change brings the Sun version of sendmail into closer compliance with the version from sendmail.org.

SPARC: 64-bit Packages

The Solaris operating environment is currently delivered in separate packages for 32-bit and 64-bit components. The 64-bit packages, introduced in the Solaris 7 release, deliver the 64-bit components of the Solaris operating environment. In general, the 64-bit package name ends with the letter “x.” For example, SUNWcsl delivers the 32-bit version of the Solaris Core Libraries, and SUNWcslx delivers the 64-bit version.

In a future Solaris release, 32-bit and 64-bit components might be delivered together in a single base package. The combined package retains the name of the original 32-bit package, and the 64-bit package would no longer be delivered. For example, /usr/lib/sparcv9/libc.so.1, which is currently delivered in SUNWcslx, would be delivered in SUNWcsl and SUNWcslx would no longer be delivered.

Note –

Some packages only deliver 64-bit components and have no corresponding 32-bit package. In these cases, the packages might be renamed to remove the “x” suffix. For example, SUNW1394x might become SUNW1394.

Solaris 32-bit Sun4U Kernel

Many installations of the Solaris 7, 8, and 9 software use the default 64-bit kernel to support 32-bit and 64-bit applications. Customers who use the 32-bit kernel on UltraSPARC systems should read this notice.

In the Solaris 7, 8 and 9 operating environments, all systems that are based on the UltraSPARC I and UltraSPARC II processors provide administrators the choice of booting a 32-bit kernel or a 64-bit kernel. The UltraSPARC III and later systems support only the 64-bit kernel.

In a future release of the Solaris operating environment, the 32-bit kernel might not be available for the UltraSPARC I and UltraSPARC II systems.

The primary impact of these changes is to systems that rely on third-party, 32-bit kernel modules: firewalls, kernel-resident drivers, and replacement file systems, for example. These systems must be updated to use 64-bit versions of those modules.

Another impact of these changes is that UltraSPARC systems that contain UltraSPARC I processors with clocks that run at 200 MHz or lower frequencies might not be supported in a future release.

To identify the system's kernel type, use the isainfo(1) command.

% isainfo —kv

To identify the system's processor clock rate, use the psrinfo(1M) command.

% psrinfo —v | grep MHz

Solaris Static System Libraries

This announcement applies only to 32-bit static-system libraries and statically linked utilities. 64-bit static system libraries and utilities have never been provided.

Support for 32-bit Solaris static-system libraries and statically linked utilities might not be provided in a future release. Of particular note, support for the static C library (/usr/lib/libc.a) might not be provided in a future release.

Applications that are linked with existing static system libraries might not work in a future release. Only applications that are dynamically linked with the system libraries that provide the Solaris application binary interface (ABI) are designed for future compatibility.

Applications that depend on the behavior of system traps might not work in a future release. Applications that link with libraries that depend on the behavior of system traps, typically libraries providing substitute ABI functions, also might not work in a future release.

Solaris Volume Manager Transactional Volume

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 capability is provided by UFS Logging, included in the Solaris 8 operating environment, and compatible versions.

Solstice Enterprise Agents

Solstice Enterprise Agents might not be supported in a future release.

SPC Driver

The SPC driver might not be supported in a future release.

Standalone Router Discovery

The /usr/sbin/in.rdisc implementation of the IPv4 ICMP Router Discovery protocol might not be supported in a future release of the Solaris software. A near-equivalent version of this protocol, which is implemented as a component of /usr/sbin/in.routed, supports an enhanced administrative interface. The /usr/sbin/in.routed component supports the implementation of Routing Information Protocol (RIP) version 2. The /usr/sbin/in.routed component also has the ability to distinguish Mobile IP advertisements from Router Discovery messages.

Storage Interfaces

The following interfaces for device driver properties might not be supported in a future release of the Solaris operating environment:

The following device drivers might not be supported in a future release of the Solaris operating environment:

The following utility might not be supported in a future release of the Solaris operating environment:

sun4m Hardware

sun4m hardware might not be supported in a future release of the Solaris operating environment.

Sun StorEdge A3000, Sun StorEdge A3500, and Sun StorEdge A3500FC Systems

Software support for the following storage devices might not be provided in a future release of the Solaris operating environment:

Tape Devices

The following tape devices might not be supported in a future release of the Solaris operating environment:

Ultra AX and SPARCengine Ultra AXmp Graphics Card

Support for the UltraTM AX and the SPARCengine Ultra AXmp graphics card might not be provided in a future release of the Solaris operating environment.

32-bit: X11 Static Libraries

Static libraries in /usr/openwin/lib might not be supported in a future release of the Solaris operating environment. Support for 32-bit static libraries in /usr/openwin/lib and programs that are statically linked with those libraries might not be provided in a future release. Sixty-four-bit static libraries have never been provided.

Applications that are linked with existing static libraries in /usr/openwin/lib might not work in a future release. Only applications that are dynamically linked with the shared libraries that provide the Solaris application binary interface (ABI) are designed for future compatibility.

XIL Interface

The XILTM interface 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.

xetops Utility

The xetops utility might not be supported in a future release of the Solaris operating environment. The xetops utility converts an Asian text file to a PostScript file. This conversion enables Asian characters to be printed on PostScript printers that do not have resident Asian fonts.

Similar capability is provided in the mp command, which has been enhanced to support all of the native Asian encodings with more options and functionality.

xutops Print Filter

The xutops print filter might not be supported in a future release. Similar capability is provided by the mp print filter in the Solaris 9 8/03 operating environment.

For more information, see the mp(1) man page.