Installation guide
For your application to work with large files (for example, “large-file aware”), you
must examine and modify your source code. Examples for areas to modify include:
Output and in-memory formatting strings such as %ld to %ll
Any variable for temporary storage of sizes or offset information must be
correctly sized to avoid truncation
Function parameters and return values should be checked and corrected if
necessary.
For more information, see NFS Administration Guide and System Administration
Guide.
Versioning and Scoped Libraries
Versioning and scoping are related enhancements to the link editor in the Solaris
operating environment. Developers of dynamic objects can use these technologies to
define sequential versions of a dynamic object’s binary interface within the object and
reduce global symbols to local scope. These capabilities provide the means to control
interface evolution across software releases, inherit global symbols from previous
versions, record version dependencies, and describe internal implementation changes.
Versioning and scoping enable developers to provide stable interfaces for program
development, achieve standards compliance, and protect implementation changes
(such as bug fixes) from the object’s public interface. An added benefit can be
reduced object size and runtime relocation cost, which can improve an application’s
runtime performance.
For the Solaris 2.6 operating environment, the system libraries take advantage of this
technology and have been both scoped and versioned.
For more information, see Linker and Libraries Guide.
Scheduler Activation
Scheduler activations provide additional kernel scheduling support for
multithreaded applications. This is implemented as a private interface between the
kernel and the libthread library (or libpthread), without changing the
libthread (libpthread) interface. Among other things, this enables the thread
library to implement adaptive mutex locks. Adaptive mutex locks is where a thread
trying to acquire a lock spins if the thread holding the lock is currently running on a
processor, and blocks otherwise.
See the libsched(3X) man page for more information.
What’s New: A Closer Look 3-19