| Skip Navigation Links | |
| Exit Print View | |
|
Oracle Solaris 10 9/10 Release Notes |
2. Oracle Solaris Runtime Issues
4. End-of-Software Support Statements
Features Removed in This Release
Features That Might Be Removed in a Future Release
SYSV3 SCO Compatibility Environment Variable
Jakarta Tomcat 4 Interfaces in the Oracle Solaris 10 OS
Drivers for Various SPARC Compatible Graphics Cards
Xprt Server and Xprint Extension
xorgcfg and xorgconfig Utilities
Auditing File Size Statistics and File Size Restriction Interfaces
Some audiorecord and audioplay Application Switches
Policy Change for Inbound Open Source and Third-Party, Vendor-Supplied Open Source Components
SPARC: cg6 Driver for SBus Graphics Cards
ctlmp and ctlconvert_txt Utilities
Sun Java System Calendar Server Client Applet
GNOME Viewer for PDF and PostScript Files
Smartcard Administrative Interface
Remote Program Load Server Functionality
Transition From ipge to e1000g NIC Driver as the Default Ethernet Driver for sun4V Systems
Solstice Enterprise Agents Support
32-bit x86: Extended Memory File System Support
Standard Type Services Framework Support
Removable Volume Management Support
32-bit x86: Controller Devices and Drivers
64-bit SPARC: Dual Basic Rate ISDN Interface and Multimedia Codec Chips
SPARC: Certain Drivers Might Not Be Supported in a Future Oracle Solaris Release
Automated Security Enhancement Tool Support
Cfront Runtime Support Library
Configuration Administrations's fp Plug-In Hardware Options
Device Allocation Interfaces for the Basic Security Module
Obsolete Device Driver Interfaces
Device Management Entries in the power.conf File
Device Support and Driver Software
Form and Menu Language Interpreter
Kerberos Ticket Lifetime Parameters in krb5.conf
Legacy or Traditional Non-UTF-8 Locales
Functions in the CPU Performance Counters Library (libcpc)
Solaris Management Console Patch Tool (Patch Manager)
Oracle's Sun Fire Link Interfaces
Java Desktop System Applications
Token Ring and Fiber Distributed Data Interface Device Types
A. Previously Documented Bugs That Were Fixed in the Oracle Solaris 10 9/10 Release
The following features might not be supported in a future release of the Oracle Solaris software.
Support for the SYSV3 SCO compatibility environment variable might be removed in a future Oracle Solaris release. The following commands may be affected:
df
echo
expr
sh
tar
uname
The passmgmt command might be removed in a future Oracle Solaris release. You can use the following commands which provide the same functionality:
The localeadm(1M) command might not be available in a future Oracle Solaris release.
SER and SERWeb might not be included in a future Oracle Solaris release.
Jakarta Tomcat 4 might not be included in a future release. You can migrate to either Jakarta Tomcat 5.5 or Jakarta Tomcat 6 which provides the same functionality.
Support for the 1x branded zone might be removed in a future Oracle Solaris Zones release.
The following SPARC workstations might not be supported in a future Oracle Solaris release:
Ultra 2, 3, 5, 10, 30, 60, 80
Sun Blade 100, 500, 1000, 1500, 2000, 2500
Continue on the Oracle Solaris 10 OS for the remaining life of the hardware, and then migrate to either an x64 workstation or a Sunray desktop.
The following plotting commands might not be supported in a future release:
plot
aedplot
atoplot
bgplot
crtplot
dumbplot
gigiplot
hpplot
implot
plottoa
t300
t300s
t4013
t450
tek
vplot
hp7221plot
In addition, the -g option in LPR might no longer be supported in a future release.
MySQL 4 RDBMS might not be supported in a future release. You can migrate to MySQL 5.1 which provides the same functionality.
Apache httpd 1.3 might not be supported in a future release. You can migrate to Apache httpd 2 which provides the same functionality.
The audit_user(4) database and the getuausernam(3BSM) accessor functions might be removed in a future Oracle Solaris release. The per-user audit preselection flags might be specified differently.
The following drivers for the graphics cards on the SPARC platform might not be included in a future release of the Oracle Solaris OS:
|
The following table lists locales that might be removed in a future Oracle Solaris release. The table also lists the corresponding locales that provide the same locale data and must be used instead:
|
Support for Java SE 1.4.2 might be removed in a future release of Oracle Solaris 10. To receive critical fixes, consider the following options:
Migrate to Java SE for Business 1.4.2.
Migrate to the latest Java SE release.
For information about technology support and EOL policy, see http://java.sun.com/products/archive/eol.policy.html.
Support for Java SE 5.0 might be removed in a future release of Oracle Solaris 10. To receive critical fixes, consider the following options:
Migrate to Java SE for Business 5.0.
Migrate to the latest Java SE release.
For information about technology support and EOL policy, see http://java.sun.com/products/archive/eol.policy.html.
The following @euro locale variants might be removed in a future Oracle Solaris release:
|
Users should use the corresponding non-variant locales.
The ucblinks feature that created SunOS 4.x device name links in the /dev directory might not be supported in a future Oracle Solaris 10 release. The current release uses SunOS 5.x device names.
The following table lists the SunOS 4.x device name links that might be removed:
|
The following table lists the current SunOS 5.x device name links:
|
The Xprt server and Xprint extension to the X Window System might no longer be included in a future Oracle Solaris release. The libXp library will remain for binary compatibility. This enables existing users of this software to continue printing over the network to Xprt servers running on Oracle Solaris 10 and prior releases, or Xprint implementations on other platforms.
The xmh command might no longer be included in a future Oracle Solaris release. Thunderbird and Evolution are the supported email GUIs.
XIE libraries might no longer be included in a future Oracle Solaris release.
The bdftosnf and showsnf commands might no longer be included in a future Oracle Solaris release.
PostgreSQL versions 8.1 and 8.2 might not be supported in a future Oracle Solaris release.
Note - PostgreSQL 8.1 and all its interfaces are obsoleted in the Oracle Solaris 10 OS. You must migrate your applications to the higher PostgreSQL versions available in the Oracle Solaris OS.
The cz short variant for the Czech locale might be removed in a future Oracle Solaris release. Users should use the following Czech locales instead:
cs_CZ
cs_CZ.ISO8859-2
cs_CZ.UTF-8
cs_CZ.UTF-8@euro
The following Oracle Solaris Audit interfaces might be replaced with equivalent functionality in a future release of Oracle Solaris:
audit_startup(1M)
bsmconv(1M)
bsmrecord(1M)
bsmunconv(1M)
audit_control(4)
The xorgcfg and xorgconfig utilities for generating xorg.conf files might no longer be available in a future Oracle Solaris release.
The Xorg(1) server does not require an xorg.conf(4) file in many cases and will autoconfigure itself if the file is not present. Users should use one of the following alternative methods to generate an xorg.conf file for customization if the default configuration does not meet their needs:
When the server is not already running, /usr/X11/bin/Xorg -configure, provides a sample configuration file for the currently detected hardware in the system.
When Xorg is started without a configuration file, the xorg.conf data that Xorg automatically generates is logged in the /var/log/Xorg.0.log log file. The xorg.conf data might also be copied to an xorg.conf file for customization.
Users of NVidia graphics devices should use the provided nvidia-settings(1) and nvidia-xconfig(1) utilities to generate or update device-specific configurations.
Users of Sun graphics devices for the SPARC platform should use the fbconfig(1) utility to generate or update device-specific configurations.
The auditing file size statistics and file size restriction interfaces getfsize and setfsize, consisting of the similarly named sub-commands within the auditon(2) system call and the options to the auditconfig(1M) command, might not be supported in a future Oracle Solaris release.
Oracle Berkeley DB (BDB) 4.2 might not be supported in a future Oracle Solaris release.
The -p and -b switches to both the audiorecord and audioplay applications, as well as the -m switch to audiorecord might be removed in a future Oracle Solaris release.
If a filename is not specified on the command line and standard input and output is not a tty, both these applications will exit with an error. Any changes to audio volume settings made by these applications are not persistent from one instance to the next. Users wishing to adjust the settings of their audio devices should migrate to the mixerctl(1) and gnome-volume-control(1) applications.
The Oracle Solaris 10 OS might no longer be available on CDs in future Oracle Solaris releases.
When the Open Source Community stops the development of inbound Open Source components like Mozilla, Sun will also stop all the development and support activities of this product version. Sun will publish a Managed Products End-of-Software Support List (EOSL) at http://www.sun.com/service/index.jsp and update the list monthly with the components that will no longer be supported.
Starting from the Solaris 10 10/08 release, the Mozilla 1.X software is no longer supported as a result of the new Inbound Open Source components policy change. Users should upgrade to Firefox.
The Sound Blaster Pro device driver (sbpro) for SoundBlaster Pro, SoundBlaster 16, and SoundBlaster AWE32 ISA devices might not be supported in a future release.
The CacheFS file system feature might not be supported in a future Oracle Solaris release.
sdtudctoolCommand might not be available in a future Oracle Solaris release. For more information, see User Defined Characters Migration Guide for the migration at http://developers.sun.com/global/products_platforms/solaris/reference/techart/UDCGuide.html
The cg6 driver for the following SBus graphics cards might not be included in a future release:
GX
GXplus
TurboGX
TurboGXplus
The /usr/openwin/bin/ctlmp and /usr/openwin/bin/ctlconvert_txt utilities might not be supported in a future Oracle Solaris release. Users should use mp(1) print filter or another suitable printing mechanism instead.
The genlayouttbl(1) utlity which provides complex text layout data to the CDE/Motif GUI toolkit might not be available in a future release.
The Mobile IPv4 feature described in the mipagent(1M) man page, might not be available in a future Oracle Solaris release.
Gnopernicus, the Java DS Screen Reader might not be available in a future Oracle Solaris release. Users should use the Orca Screen Reader instead.
The Xsun server for the X Window System might not be available in a future Oracle Solaris release. Users should migrate to the Xorg server.
Features such as Display Postscript (DPS) and X Image Extension (XIE) that are available in Xsun but not in Xorg might no longer be included.
The Common Desktop Environment (CDE) might not be available in a future Oracle Solaris release. Users should migrate to the Java Desktop System.
CDE's Image Viewer sdtimage might not be available in a future Oracle Solaris release. Users should migrate to GNOME Open gnome-open, to open image files.
The Sun Java System Calendar Server client applet, Now applet, might not be available in a future Oracle Solaris release.
The DARPA trivial name server, in.tnamed(1M), might not be available in a future Oracle Solaris release. The Internet domain name server named(1M) provides similar functionality.
The I2O intelligent I/O driver framework and all corresponding drivers might not be supported in a future Oracle Solaris release. This includes the i2o_bs(7D), and i2o_scsi(7D) drivers and all I2O related functionality.
The GNOME viewer for PDF and PostScript files, might not be available in a future Oracle Solaris release. A replacement application is expected to enable viewing of PDF and PostScript files.
The graphical Smartcard admin interface sdtsmartcardadmin(1M) may not be available in future Oracle Solaris releases. The same functionality is available in the smartcard(1M) command.
The Dallas Semiconductor iButton Java Card Smartcard and OpenCard Framework (OCF) terminal driver, as described in ocf_ibutton(7d) might not be supported in future Oracle Solaris releases. Users should migrate to other Smartcard devices that are supported by libpcsclite(3lib).
The Cyberflex Smartcard might not be supported by the pam_smartcard(5) and smartcard(1m) commands in future Oracle Solaris releases. Users should migrate to other Smartcard devices and cards that are supported by libpcsclite(3lib).
The PAM Smartcard module pam_smartcard(5) might not be available in future Oracle Solaris releases.
The OCF/SCF Smartcard framework may not be available in a future Oracle Solaris releases. The functionality of ocfserv(1M) will be provided by pcscd(1M). The card provisioning functionality of smartcard(1M) will be provided by muscletool(1M). The driver configuration functionality provided by smartcard(1M) is generally not necessary with pcscd(1M), however, when required system administrators can edit the reader.conf(4) file.
The SmartCard Framework (SCF) interfaces exported by libsmartcard and smartcard.jar may not be available in future Oracle Solaris releases. These interfaces are now obsolete. New C applications should be written to use the PS/SC interfaces exported from libpscslite(3lib). There is no planned replacement for the SCF Java interfaces at this time.
The Remote Program Load (RPL) server functionality available through rpld(1M) and rpld.conf(4) may not be available in a future release of Oracle Solaris.
The ipge driver and all its SUNWipge packages for sun4V systems might not be available in a future release of Oracle Solaris. Starting with the Solaris 10 8/07 release, Ontario and other SPARC based platforms transition from ipge to e1000g drivers. The e1000g driver will be the default Ethernet driver for all Sun platforms that use Intel 1G chipsets.
The following Solstice Enterprise Agents (SEA) agents, libraries, and packages might not be supported in a future Oracle Solaris release:
SEA-based SNMP master agent and sub agents
libssagent and libssasnmp libraries
SUNWsacom, SUNWsasnm, SUNWmibii packages
The System Management Agent (SMA) provides similar functionality for the aforementioned sources.
The extended memory file system (xmemfs) might not be supported in a future Oracle Solaris release.
For more information, see the xmemfs(7FS) man page.
Standard Type Service Framwork (STSF) might not be available in a future Oracle Solaris release.
This includes the following:
libST and libXst libraries
xstls command
stfsloader service
XST extension to Xsun and Xorg servers
You can find this functionality in one of the following alternative sources:
libX11
libXft2
The JNI Fibre Channel Adapter (jfca) driver might not be available in a future Oracle Solaris release.
For more information, see the jfca(7D) man page.
The -s option in the zic command might not be available in a future Oracle Solaris release.
For more information, see the zic(1M) man page.
The volume management daemon (vold), volume management file system (volfs), and the associated volume management commands might not be included in a future Oracle Solaris release.
Automatic mounting and unmounting of removable media will continue to be supported.
For more information, see the vold(1M) and volfs(7FS) man pages.
The following devices might not be supported in a future Oracle Solaris release:
IBM PC ServeRAID SCSI
IBM ServeRAID II Ultra SCSI
IBM ServeRAID-3 Ultra2 SCSI
In addition, device drivers written for these controllers might not be supported.
T5900FC Dual Basic Rate ISDN Interface (DBRI) and associated multimedia codec chips might not be supported in a future Oracle Solaris release. In addition, device drivers written for these devices might not be supported.
The following drivers might not be supported in a future Oracle Solaris release:
SUNWrtvc: Device driver for the SunVideo real-time video capture and compression card
SUNWdial: Streams module for the Dials and Buttons devices
SUNWdialh: Header files for the Dials and Buttons devices
The checksum functionality provided by Automated Security Enhancement Tool (ASET) in the /usr/aset directory might not be available in a future Oracle Solaris release.
You can find this functionality in one of the following alternative sources:
The basic audit reporting tool, bart, in the Oracle Solaris 10 OS
The Solaris Security Toolkit found at http://www.sun.com/software/security/jass/
The Solaris Fingerprint Database found at http://sunsolve.sun.com/pub-cgi/show.pl?target=content/content7
The following Asian short locale names might not be listed in the dtlogin language list in a future release:
zh
ko
zh_TW
Beginning with Solaris 8 release, new ISO-standard locale names have been provided, including the following locale names:
zh_CN.EUC
zh_CN.GBK
zh_CN.UTF-8
ko_KR.EUC
ko_KR.UTF-8
zh_TW.EUC
The following interfaces that are used by the Solaris audit daemon might not be supported in a future release:
The library libC.so.3 is the runtime support library for programs that are compiled by the Cfront C++ compiler C++ 3.0. Neither the compiler nor programs that are created by the compiler run on Oracle Solaris 10 OS. The library might not be supported in a future release of Oracle Solaris.
The following options of the configuration administration's (cfgadm) fp plug-in might not be supported in a future Oracle Solaris release:
show_FCP_dev
unusable_FCP_dev
The following components of the device allocation mechanism of the Basic Security Module might not be included in a future release of the Oracle Solaris software:
/etc/security/dev
Some device driver interfaces (DDI) might not be supported in a future release.
The following table lists the DDI interfaces that might not be supported, along with the preferred DDI interface alternatives.
|
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 Oracle Solaris software.
For more information, see the power.conf(4) man page.
The following table lists devices and driver software that might not be supported in a future release.
Table 4-1 Device and Driver Software
|
The Form and Menu Language Interpreter (FMLI) commands are obsolete and might not be supported in a future Oracle Solaris release. The obsolete commands include the following:
/usr/bin/fmli
/usr/bin/vsig
The host files in /etc/net/ti* are no longer consulted in the Oracle Solaris OS, though these files remain in the software. In a future Oracle Solaris release, these host files might be entirely removed.
The Kerberos Ticket Lifetime parameters, max_life and max_renewable_life, might no longer be supported in a future release of the Oracle Solaris OS. These parameters are in the appdefaults section of the /etc/krb5/krb5.conf file. Instead of these parameters, use max_lifetime and renew_lifetime in the libdefaults section of /etc/krb5/krb5.conf.
Korean CID fonts will not be supported in a future release. You can use the Korean TrueType fonts that are included in the Oracle Solaris software as a replacement for Korean CID fonts.
Sun is adopting Unicode for character encoding. Therefore, except for zh_CN.GB18030 and C locales, non-UTF-8 locales might be removed as the Java Desktop System login locale in a future Oracle Solaris release.
Hardware performance counters enable the measurement of many different hardware events that are related to CPU behavior. The following functions in the CPU Performance Counters library (libcpc) might not be supported in a future Oracle Solaris OS release:
|
New functions have been added to the library in the Oracle Solaris 10 OS. Developers who have code that utilizes the interfaces in the preceding list should instead use the following corresponding new functions:
|
See the cpc(3CPC) man page for details.
The libXinput.so.0 library might not be provided in a future release of the Oracle Solaris software. 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.
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 software. For more information, visit http://www.sun.com/directory/nisplus/transition.html.
The nstest is an interactive DNS test program to construct and send DNS queries. This program might no longer be supported in a future Oracle Solaris OS release. The same functionality that is provided by this test program is available by using the dig and nslookup commands.
Perl version 5.6.1 might not be supported in a future Oracle Solaris OS release. Perl version 5.8.4, the default version in the Oracle Solaris 10 OS, is not binary compatible with Perl version 5.6.1. However, the earlier version is still retained in this release. Customized modules that are installed by the customer must be rebuilt and reinstalled to use Perl version 5.8.4. Modify any scripts that require the use of version 5.6.1 to specifically use version 5.6.1 of the interpreter instead of version 5.8.4. The interpreters of the respective Perl versions are located in the following directories:
/usr/perl5/5.6.1/bin/perl
/bin/perl, /usr/bin/perl, or /usr/perl5/bin/perl
The Oracle Solaris Management Console patch tool, Patch Manager, might not be available in a future release.
Solstice Enterprise Agents might not be supported in a future release.
The /usr/sbin/in.rdisc implementation of the IPv4 ICMP Router Discovery protocol might not be supported in a future release of the Oracle 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.
The Oracle Sun Fire Link Interfaces might no longer be supported in a future Oracle Solaris release.
The following applications in the Java DS, Release 3, might be removed from a future release.
Sun Java Calendar Preview
GNOME Keyboard Layout Switcher
Java DS Diagram Editor
Java DS Java Text Editor
Java DS Java Dictionary
Java DS Disk Analyzer
Java DS Mr. Project
Support for token ring (DL_TPR) and Fiber Distributed Data Interface (FDDI) device types in generic LAN driver (GLD) might be removed in a future Oracle Solaris release. After the removal is implemented, drivers for token ring or FDDI that rely on this support in GLD cease to function. However, other drivers or applications that do not use this support are not affected. To test whether a driver relies on GLD, run the following script:
#!/bin/sh
#
# Test a driver binary for use of GLD
#
for file
do
/usr/ccs/bin/nm $file | /bin/awk '
/\|gld_register$/ { isgld=1; }
END {
if (isgld)
print file, "uses GLD";
else
print file, "does not use GLD";
}' file=$file
done
For more information about generic LAN driver, see the gld(7D) man page as well as “Writing Device Drivers”.
The feature known as WDR - Web-Based Enterprise Management Dynamic Reconfiguration - might not be supported in a future release of the Oracle Solaris OS. WDR is currently supported on Sun Fire midrange and high-end systems.
The XIL 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.
The xetops utility might not be supported in a future release. 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.
Certain DDX modules for Xsun might be removed from a future Oracle Solaris release. These modules are used when you configure the Xsun X server on the kdmconfig screen, Video Device Selection, by selecting an entry that is not prefixed with “XF86.” The files affected by this notice include the following:
Files in the /usr/openwin/server/modules directory whose names do not have the ddxSUNWxf86 prefix
The /usr/openwin/server/lib/libaccel.so.1 library
Files with the .xga suffix under the /usr/openwin/share/etc/devdata/SUNWaccel/boards directory
It is recommended that for your preferred X server, use the Xorg X server whose DDX modules provide comparable functionality to the Xsun X server. However, if you use the Xsun X server, you can still use the XFree86 DDX modules. These are modules with the prefix ddxSUNWxf86 and whose entries in the kdmconfig screen, Video Device Selection, begin with “XF86.” These modules provide comparable functionality to the Xsun DDX modules that might be removed.
|