|Skip Navigation Links|
|Exit Print View|
|Oracle Solaris 10 1/13 Release Notes Oracle Solaris 10 1/13 Information Library|
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:
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:
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.