Skip Navigation Links | |
Exit Print View | |
Oracle Solaris 10 1/13 Release Notes Oracle Solaris 10 1/13 Information Library |
3. Oracle Solaris Runtime Issues
Recommended Adoption of SHA-256 and SHA-512 crypt Plug-ins for Password Encryption
System Might Encounter Data Integrity Issues (15825389)
System Reboots Continuously Because of a ZFS-Related Panic (15809921)
ZFS and UNIX/POSIX Compliance Issues
fdisk -E Command Can Sweep Disk Used by ZFS Without Warning (15325067)
BrightStor ARCserve Backup Client Agent for UNIX (Solaris) and ZFS Support Issue
ZFS GUI Should Check for /usr/lib/embedded_su Patch at the Beginning of Each Wizard (15287937)
Upgrading From Some Oracle Solaris 10 Releases Requires Remounting of File Systems
NFSv4 Access Control List Functions Might Work Incorrectly
Hardware-Related Issues and Bugs
SPARC: Dynamic Reconfiguration Operations Fail on an OPL Platform (15725179)
x64: PCI Subsystem ID Changes in ConnectX Firmware 2.6.0 From Mellanox (15544691)
The ZFS ARC Allocates Memory Inside the Kernel Cage Preventing DR (15377173)
Certain USB 2.0 Controllers Are Disabled
Supported USB Devices and Corresponding Hub Configurations
x86: Limitations Exist With Certain Device Drivers in the Oracle Solaris 10 OS
DVD-ROM/CD-ROM Drives on Headless Systems
x86: Manual Configuration Required to Specify Non-U.S. English Keyboards
Programs Compiled With Some Options of Oracle Solaris Studio Do Not Run (16237300)
Firefox and Thunderbird Hang in the Hangul Input Method (16043053)
Swedish Software Translations Note
Multiple Input Method Switcher Applications Appear in Trusted Java Desktop System
x86: Arabic Text Not Appearing in ar Locales
Migration Note for UTF-8 Locales
Emails Saved as Portable Format
File Names and Directory Names
Launching Legacy Locale Applications
Hardware for Some Keyboard Layouts Type 6 and 7 Not Available
System Domain of Interpretation Is Not Configurable (15283123)
IP Forwarding Is Disabled by Default in the Oracle Solaris 10 OS
Oracle Solaris Commands and Standards
Changed Man Pages for Trusted Extensions Are in Reference Manual Only
New ln Utility Requires -f Option
New tcsh Version Rejects setenv Variable Names That Use a Dash or an Equal Sign
Solaris Volume Manager Does Not Remove Devices Correctly If fdisk Does Not Have Valid Entries
Solaris Volume Manager metattach Command Might Fail
Email and Calendar Application
Problem With Changing Authentication Type (15256650)
User Preferences Not Fully Compatible
x86: Cannot Configure Full-Screen Magnification on Systems With One Video Card
System Administration Issues and Bugs
Oracle VTS fputest Fails on Fujitsu M10 Systems (15989998)
Oracle VTS testprobe_ramtest Fails on Fujitsu M10 Systems (15955560)
Oracle VTS testprobe_l3sramtest Fails on Fujitsu M10 Systems (15955589)
Crash Dump Is Saved in the /var/crash Directory (15767302)
Using DISM Might Cause the System to Hang (15807808)
x86: Running the ludelete Command Can Delete Shared Datasets Not Related To the OS (15817477)
Oracle Solaris 10 9/10 Clock Stops on Oracle VM 2.2 (15643194)
SPARC: FKU 137137-xx Patch Does Not Support Third-Party Volume Manager Software
Sun Patch Manager Tool 2.0 Incompatible With Previous Versions of the Tool
4. End-of-Software Support Statements
A. Previously Documented Bugs That Were Fixed in the Oracle Solaris 10 1/13 Release
The following section describes behavior changes in certain commands and standards in this Oracle Solaris 10 OS release.
The following Trusted Extensions man pages are revised for this release:
add_allocatable(1M)
remove_allocatable(1M)
label_to_str(3TSOL)
tsol_getrhtype(3TSOL)
tnzonecfg(4)
The revised man pages cannot be viewed using the man command. To view the revised man pages, see the Solaris Trusted Extensions Reference Manual.
The behavior of /usr/bin/ln has changed to adhere to all of the standards from SVID3 through XCU6. If you use the ln command without the -f option to link to an existing target file, the link is not established. Instead, a diagnostic message is written to standard error, and the command proceeds to link any remaining source files. Finally, the ln command exits with an error value.
For example, if file b exists, the syntax ln a b generates the following message:
ln: b: File exists
This behavior change affects existing shell scripts or programs that include the ln command without the -f option. Scripts that used to work might now fail in the Oracle Solaris 10 OS.
Workaround: Use the -f option with the ln command. If you have existing scripts that execute the link utility, make sure to modify these scripts to comply with the command's new behavior.
In the Oracle Solaris 10 OS, tcsh has been upgraded to version 6.12. This version no longer accepts environment variables whose names use a dash or an equal sign. Scripts that contain setenv lines and that work in earlier Oracle Solaris versions might generate errors in the current release. The following error message is displayed:
setenv: Syntax error
For more information, see the tcsh man page.
Workaround: Do not use the dash or equals sign in names for environment variables.
Applications that were built in strict standard C conformance mode are affected by the behavior changes of certain library functions. An example is applications that were compiled by using the cc -Xc or c89 compilation mode. The behavior has changed for the following library functions:
fgetc()
fgets()
fgetwc()
fgetws()
getc()
getchar()
gets()
getwc()
getwchar()
getws()
A formal interpretation of the 1990 C Standard requires that after an end-of-file condition is set, no more data is returned from the file on subsequent input operations unless the file pointer is repositioned or the error and end-of-file flags are explicitly cleared by the application.
The behavior for all other compilation modes remains unchanged. Specifically, the interfaces can read additional newly written data from the stream after the end-of-file indicator has been set.
Workaround: Call the fseek() or clearerr() function on the stream to read additional data after the EOF condition has been reported.
The columns of the ps command output have been widened because of larger UIDs, processor IDs, and cumulative execution time. Scripts should no longer assume fixed output columns.
Workaround: Scripts should use the -o option of the ps command.
For more information, see the ps(1) man page.