| Skip Navigation Links | |
| Exit Print View | |
|
Oracle Solaris 10 8/11 Release Notes Oracle Solaris 10 8/11 Information Library |
| Skip Navigation Links | |
| Exit Print View | |
|
|
Oracle Solaris 10 8/11 Release Notes Oracle Solaris 10 8/11 Information Library |
3. Oracle Solaris Runtime Issues
4. End-of-Software Support Statements
Features Removed in This Release
Features That Might Be Removed in a Future Release
rstart Client and rstartd Server
-x and -C Options in the vi, ex, and ed Commands
Sun OpenGL Software From Oracle for the SPARC Platform
Boot Support in Solaris Volume Manager From Oracle
ioctls Floppy Driver and fdformat Utility
Replacing /etc/power.conf and pmconfig With poweradm
Replacing Trusted Extensions IPv6 CIPSO With CALIPSO
Flash Archive Installation Commands
Removal of QLogic SCSI Ultra160 Device Driver
32-bit SPARC and x86: libmle Library
32-bit SPARC: Removal of Asian SunOS4.x BCP
32-bit SPARC and x86: Removal of Legacy Asian Print Filters
32-bit SPARC and x86: Removal of Legacy Asian Libraries
32-bit SPARC and x86: Removal of Legacy Asian Commands
SPARC: SunOS 4 Binary Compatibility Support
x86: 32-bit X Servers and Drivers
SYSV3 SCO Compatibility Environment Variable
Jakarta Tomcat 4 Interfaces in the Oracle Solaris OS
Auditing File Size Statistics and File Size Restriction Interfaces
Drivers for Various SPARC Compatible Graphics Cards
Xprt Server and Xprint Extension
xorgcfg and xorgconfig Utilities
Some audiorecord and audioplay Application Switches
Policy Change for Inbound Open-Source and Third-Party, Vendor-Supplied Open-Source Components
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 sun-4v Systems
Solstice Enterprise Agents Support
32-bit x86: Extended Memory File System Support
Standard Type Services Framework Support
Removable Volume Management Support
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 the krb5.conf File
Legacy or Traditional Non-UTF-8 Locales
Functions in the CPU Performance Counters Library (libcpc)
Solaris Management Console Patch Tool (Patch Manager)
Oracle 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 8/11 Release
The following features might not be supported in a future release of the Oracle Solaris software.
The LP print service might not be included in a future Oracle Solaris release.
Support for legacy systems that have included the UltraSPARC I, II, IIe, III, IIIi, III+, IV, and IV+ processor architectures, as reported by the Oracle Solaris psrinfo -pv command, might be removed from a future Oracle Solaris release. All SPARC Enterprise M-Series servers and SPARC T-Series servers will continue to be supported.
Note - Oracle Solaris 10 will continue to be a supported operating system for these affected platforms as per the current Oracle lifetime support policy.
The following SPARC workstations might not be supported in a future Oracle Solaris release:
Ultra 2, 3, 5, 10, 30, 60, and 80
Sun Blade 100, 500, 1000, 1500, 2000, and 2500
Continue using the Oracle Solaris 10 OS for the remaining life of the hardware. Then, migrate to either an x64 workstation or a Sun Ray desktop.
The rstart client and rstartd server might not be included in a future Oracle Solaris release. To start an X Window system program on another machine, use the X11 forwarding feature of the ssh(1) command.
The rdist command might be removed in a future Oracle Solaris release.
The crypt(1) command might be removed in a future Oracle Solaris release. Instead, you can use the encrypt(1) command, which provides access to new and secure algorithms, to protect your files.
The encrypt(1) command is available starting from this Oracle Solaris 10 release.
The -x and -C options for the vi(1), ex(1), and ed(1) commands might be removed in a future Oracle Solaris release. Instead, you can use the encrypt(1) command, which provides access to new and secure algorithms, to protect your files.
The encrypt(1) command is available starting from this Oracle Solaris 10 release.
Managing the configuration of an Oracle Solaris instance by using the sysidtool(1M) framework might not be possible in a future Oracle Solaris release. You can use the smf(5) system configuration framework for managing the configuration of an Oracle Solaris instance.
The Sun OpenGL software from Oracle for the SPARC platform might no longer be included in a future Oracle Solaris release. Instead, you can use the Mesa implementation of libGL or the Nvidia OpenGL provided for Nvidia graphics devices on the x64 platform, which provide the same functionality.
The Oracle Solaris FTP server based on WU-ftpd might not be available in a future release of the Oracle Solaris OS. The WU-ftpd server might be replaced with a new FTP server.
The ability to boot from a Solaris Volume Manager (SVM) metadevice might not be supported in the next release of the Oracle Solaris OS.
The ioctls (fdio) floppy driver and the fdformat utility might be removed in the next Oracle Solaris release. However, the support for the USB floppy will continue.
Note - The floppy drivers fd and fdc are already removed.
The tnf tracing (3TNF) facility might not be available in a future Oracle Solaris release. Instead, use dtrace(1M) for tracing purposes.
The /etc/power.conf configuration file and the pmconfig(1M) utility might be replaced with the poweradm(1M) command in a future Oracle Solaris release. The number of properties that can be configured with the poweradm(1M) command will be minimal.
Oracle might replace the IPv6 Commercial Internet Protocol Security Option (CIPSO) implementation with the IETF CALIPSO standard in a future Oracle Solaris release.
Commercial Internet Protocol Security Option (CIPSO), defined in FIPS PUB 188, is a standard for IPv4. The Trusted Extensions feature of Oracle Solaris has a proprietary IPv6 implementation of CIPSO because no CIPSO equivalent standards existed for IPv6 when Trusted Extensions was released.
IETF has now produced a CIPSO equivalent standard for IPv6, called Common Architecture Label IPv6 Security Option (CALIPSO) or RFC 5570.
The current CIPSO IPv4 support is not affected. CIPSO and CALIPSO are used by Trusted Extensions only.
The /etc/hostname.interface files that are used to store persistent network configuration might be removed in a future Oracle Solaris release.
The following flash archive installation commands might not be included in a future Oracle Solaris release:
flar(1M)
flarcreate(1M)
In addition, installations performed by using the flash_archive(4) file format might not be supported.
The lsimega(7d) driver might not be included in a future release. If you are using devices that are driven by lsimega(7d), migrate to glm(7d) or upgrade to more recent hardware.
The qus device driver might be removed from a future Oracle Solaris release. The qus device driver supports the QLogic Ultra160 SCSI host bus adapter.
The libmle library might not be included in a future Oracle Solaris release.
The support for all versions of Asian SunOS4 BCP might not be included in a future Oracle Solaris release. However, you can continue to use all versions of Asian SunOS4 BCP in Oracle Solaris 10 branded zones.
The following legacy Asian print filters might not be included in a future Oracle Solaris release:
big5.epson.filter(1)
cns.epson.filter(1)
jprconv(1)
jpostprint(1)
jtops(1)
thaifilter(1)
For text to PS conversion, use the mp(1) filter.
The following legacy Asian libraries, including their xctype macros, might not be included in a future Oracle Solaris release:
libcle
libhle
libkle
Instead of these libraries, use the standard functions iconv(3C) and wctype(3C). Note that you might be able to use these libraries in Oracle Solaris 10 branded zones.
The following Asian legacy commands might not be included in a future Oracle Solaris release:
EUC capable mailx(1), talk(1), in.comsat(1M), and install_comsat(1M) under the /usr/SUNWale/bin directory
Legacy utilities such as jaio.h(7i), jtty(1), kanji(1), evftobdf(1), runb5(1), and mkcodetab(1)
Legacy code set that include the following converters:
ja locale – euctoibmj ibmjtoeuc euctojis jistoeuc euctosj sjtoeuc jistosj sjtojis
ko locale – wansungtojohap johaptowansung comptonb nbtocomp comptopack packtocomp
zh locale – cgbtoeuc euctocgb cnstoeuc euctocns
zh_TW locale – big5toeuc euctobig5 cnsconv
Use the iconv(1) command instead of the legacy code set converters. Note that you might be able to use these commands in Oracle Solaris 10 branded zones.
The diskless client functionality might not be supported. The following commands might be affected:
smdiskless(1M)
smoservice(1M)
All versions of the SunOS 4 binary compatibility support might not be included in a future Oracle Solaris release. However, the support for all versions of SunOS 4 binaries will continue when used in Oracle Solaris 10 branded zones.
The sk98sol driver for SysKonnect/Marvell SK-Net gigabit Ethernet devices might be removed in a future Oracle Solaris release.
IP-forwarding SMF services manage system-wide forwarding configuration. The following IP-forwarding SMF services might be removed in a future Oracle Solaris release:
svc:/network/ipv4-forwarding:default
svc:/network/ipv6-forwarding:default
The 32-bit versions of the following X servers for x86 platforms might not be included in a future Oracle Solaris release:
Xephyr
Xorg
Xvfb
Xvnc
Note - SPARC platforms provide only the 64-bit versions of these servers.
Any Xorg loadable module, including video drivers, input device drivers, and extensions, that are not provided in a 64-bit version will not be used. If a usable video driver is not found, Xorg will use the vesa driver.
The following table shows x86 video devices that include the Xorg drivers in 32-bit versions.
|
The man pages for each driver give more information on the supported devices. If you want to build and support the driver yourself, the source for these drivers is available from the X.Org foundation at http://www.x.org/.
Support for the SYSV3 SCO compatibility environment variable might be removed in a future Oracle Solaris release. The following commands might 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 instead, 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 Oracle Solaris release. You can migrate to either Jakarta Tomcat 5.5 or Jakarta Tomcat 6, which provide the same functionality.
The lx brand uses the branded zones framework to enable Linux binary applications to run unmodified on a machine with an Oracle Solaris OS kernel.
Support for the lx 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 using the Oracle Solaris 10 OS for the remaining life of the hardware. Then, migrate to either an x64 workstation or a Sun Ray desktop.
The following plotting commands might not be supported in a future Oracle Solaris release:
aedplot
atoplot
bgplot
crtplot
dumbplot
gigiplot
hp7221plot
hpplot
implot
plot
plottoa
vplot
t300
t300s
t4013
t450
tek
In addition, the -g option of LPR might no longer be supported in a future Oracle Solaris release.
MySQL 4 RDBMS might not be supported in a future Oracle Solaris release. You can migrate to MySQL 5.1, which provides the same functionality.
Apache httpd 1.3 might not be supported in a future Oracle Solaris 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 interfaces that are used by the Oracle Solaris audit daemon might not be supported in a future release:
The following Oracle Solaris audit interfaces might be replaced with an equivalent functionality in a future release of Oracle Solaris:
audit_control(4)
audit_startup(1M)
bsmconv(1M)
bsmrecord(1M)
bsmunconv(1M)
The auditing file size statistics and file size restriction interfaces getfsize and setfsize, consisting of the similarly named subcommands within the auditon(2) system call and the options to the auditconfig(1M) command, might not be supported in a future Oracle Solaris release.
The following drivers for graphics cards on the SPARC platform might not be included in a future Oracle Solaris release.
|
The following table lists locales that might be removed in a future Oracle Solaris release. The table also lists the corresponding replacement locales.
|
Support for Java Platform, Standard Edition (Java SE) 1.4.2 might be removed in a futureOracle Solaris release. 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 the technology support and EOL policy for Java SE, see http://www.oracle.com/technetwork/java/eol-135779.html.
Support for Java SE 5.0 might be removed in a future Oracle Solaris release. 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://www.oracle.com/technetwork/java/eol-135779.html.
The following @euro locale variants might be removed in a future Oracle Solaris release:
|
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 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 library enables existing users of this software to continue printing over the network to Xprt servers running 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 applications.
X Imaging Extension (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 a later PostgreSQL version available in the Oracle Solaris OS.
The cz short variant for the Czech locale might be removed in a future Oracle Solaris release. Use the following Czech locales instead:
cs_CZ
cs_CZ.ISO8859-2
cs_CZ.UTF-8
cs_CZ.UTF-8@euro
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. Use one of the following alternative methods to generate an xorg.conf file for customization if the default configuration does not meet your 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 the Xorg server 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.
Oracle Berkeley DB 4.2 might not be supported in a future Oracle Solaris release.
The -p and -b switches in both the audiorecord and audioplay applications, as well as the -m switch in 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 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. If you want to adjust audio device settings, migrate to the mixerctl(1) and gnome-volume-control(1) applications.
When the open-source community stops the development of inbound open-source components such as Mozilla projects, Oracle will also stop all the development and support activities of that product version. Component End of Life announcements will appear in the Release Notes document.
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 Sound Blaster Pro, Sound Blaster 16, and Sound Blaster AWE32 ISA devices might not be supported in a future Oracle Solaris release.
The CacheFS file system might not be supported in a future Oracle Solaris release.
The sdtudctool command might not be available in a future Oracle Solaris release. For more information, see User Defined Characters Migration Guide at http://developers.sun.com/global/products_platforms/solaris/reference/techart/UDCGuide.html
The /usr/openwin/bin/ctlmp and /usr/openwin/bin/ctlconvert_txt utilities might not be supported in a future Oracle Solaris release. Use the mp(1) print filter or another suitable printing mechanism.
The genlayouttbl(1) utility which provides complex text layout data to the CDE/Motif GUI toolkit might not be available in a future Oracle Solaris 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 Desktop System Screen Reader might not be available in a future Oracle Solaris release. 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.
The Sun Java System Calendar Server client applet, Now, 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 technology 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 might be provided to enable viewing of PDF and PostScript files.
The Smartcard administrative graphical interface sdtsmartcardadmin(1M) might not be available in a future Oracle Solaris release. The same functionality is available through the smartcard(1M) command.
The Dallas Semiconductor iButton Java Card Smartcard and OpenCard Framework (OCF) terminal driver, as described in the ocf_ibutton(7d) man page, might not be supported in a future Oracle Solaris release. Migrate to other Smartcard devices that are supported by the libpcsclite(3LIB) utility.
The Cyberflex Smartcard might not be supported by the pam_smartcard(5) and smartcard(1M) commands in a future Oracle Solaris release. Migrate to other Smartcard devices and cards that are supported by the libpcsclite(3LIB) utility.
The PAM Smartcard module pam_smartcard(5) might not be available in a future Oracle Solaris release.
The OCF/SCF Smartcard framework might not be available in a future Oracle Solaris release. 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 accordingly.
The SmartCard Framework (SCF) interfaces exported by libsmartcard and smartcard.jar might not be available in a future Oracle Solaris release. 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) might not be available in a future Oracle Solaris release.
The ipge driver and all its SUNWipge packages for sun4v systems might not be available in a future Oracle Solaris release. Starting with the Solaris 10 8/07 release, Ontario and other SPARC based platforms transition from ipge to e1000g drivers. The e1000g driver is the default Ethernet driver for all Oracle 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 subagents
libssagent and libssasnmp libraries
SUNWsacom, SUNWsasnm, SUNWmibii packages
The System Management Agent (SMA) provides similar functionality for these resources.
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.
The Standard Type Services Framework (STSF) might not be available in a future Oracle Solaris release.
This framework 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 of 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.
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 the Automated Security Enhancement Tool (ASET) in the /usr/aset directory will be deprecated in a subsequent release. To replicate the functionality, use the Basic Audit Reporting Tool (BART), which is available at /usr/bin/bart.
The following Asian short locale names might not be listed in the dtlogin language list in a future release:
ko
zh
zh_TW
Beginning with the Solaris 8 release, the following ISO-standard locale names are provided:
ko_KR.EUC
ko_KR.UTF-8
zh_CN.EUC
zh_CN.GBK
zh_CN.UTF-8
zh_TW.EUC
The libC.so.3 library 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 the Oracle Solaris 10 OS. The library might not be supported in a future release of Oracle Solaris.
The following options of the configuration administration (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 Oracle Solaris release:
/etc/security/dev
Some device driver interfaces (DDI) might not be supported in a future Oracle Solaris release.
The following table lists the DDIs that might not be supported, along with the preferred DDI alternatives.
|
The Device Management entries in the power.conf file might not be supported in a future Oracle Solaris release. Similar capability is provided by the Automatic Device Power Management entries in the Oracle Solaris OS.
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 Oracle Solaris 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 checked in the Oracle Solaris OS, although these files remain in the software. In a future Oracle Solaris release, these host files might be removed.
The Kerberos Ticket Lifetime parameters, max_life and max_renewable_life, might no longer be supported in a future Oracle Solaris release. 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 the /etc/krb5/krb5.conf file.
Korean CID fonts will not be supported in a future Oracle Solaris release. You can use the Korean TrueType fonts that are included in the Oracle Solaris OS as a replacement for Korean CID fonts.
Oracle is adopting Unicode for character encoding. Therefore, non-UTF-8 locales might be removed as Java Desktop System login locales 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 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 Oracle Solaris release. 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 the Solaris 2.1 and Solaris 2.2 releases. The X11 standard X Input Extension library, libXi, was integrated in the Solaris 2.3 release.
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 Oracle Solaris release. Tools to aid in the migration from NIS+ to LDAP are available in the Solaris 9 software.
The nstest program is an interactive DNS test program to construct and send DNS queries. This program might no longer be supported in a future Oracle Solaris 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 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:
Perl 5.6.1: /usr/perl5/5.6.1/bin/perl
Perl 5.8.4: /bin/perl, /usr/bin/perl, or /usr/perl5/bin/perl
The Management Console patch tool, Patch Manager, might not be available in a future Oracle Solaris release.
Solstice Enterprise Agents might not be supported in a future Oracle Solaris release.
The /usr/sbin/in.rdisc implementation of the IPv4 ICMP Router Discovery protocol might not be supported in a future Oracle Solaris release. 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 can also 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 Java Desktop System Release 3 might be removed from a future Oracle Solaris release.
Calendar Preview
Diagram Editor
Disk Analyzer
GNOME Keyboard Layout Switcher
Java Dictionary
Java Text Editor
Mr. Project
Calendar Preview
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 devices 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 WBEM Dynamic Reconfiguration (WDR) feature might not be supported in a future Oracle Solaris release. WDR is currently supported on Oracle's Sun Fire midrange and high-end systems.
The XIL interface might not be supported in a future Oracle Solaris 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 Oracle Solaris 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 by the mp command, which has been enhanced to support all of the native Asian encodings with more options and functionality.
|