test

What's New in the Solaris 9 4/03 Operating Environment

What's New for Software Developers

Development Tool Enhancements

Description 

Release Date 

Stack Check APIs

Stack Check APIs allow for advanced interaction with stack-checking compiler support. Stack-checking compiler support is available in ForteTM 7.0. These APIs should be used in applications that are compiled with stack checking enabled. These are applications that manage their own stacks or attempt to detect their own stack overflows.

Developers who maintain their own thread library need to use the setustack interface to enable consumers of their library to compile with stack checking enabled.

See the stack_getbounds(3C), stack_setbounds(3C), stack_inbounds(3C), and stack_violation(3C) man pages.

4/03 

Memory Allocation With libumem

libumem is a user-mode (non-kernel mode) memory allocator library. libumem has features that enable you to debug memory leaks and other aberrations that involve memory usage.

This feature is used in the same way that a standard application binary interface (ABI) allocator, such as malloc(), is used. A user-mode application requests an arbitrary number of bytes of memory. Then a pointer is returned that is loaded with the address of the allocated memory.

For further information, see the libumem(3LIB) man page.

4/03 

SPARC: Sun ONE Application Server Integration

Sun ONE Application Server 7, Platform Edition (formerly iPlanet Application Server) is integrated in the Solaris 9 12/02 Update release. See Networking Enhancements.

12/02 

SPARC: Sun ONE Message Queue

The Solaris 9 12/02 Update release supports JMS messaging applications. These applications are based on Sun ONE Message Queue, a JMS provider. See Networking Enhancements.

12/02 

Enhanced crypt() Function

This Solaris release includes new extensions to the crypt() function and introduces the crypt_gensalt()function. These enhancements allow administrators to change the algorithm that is used to obscure users' UNIX® login passwords.

Modules are included for MD5 and Blowfish. The MD5 modules are at crypt_sunmd5 and crypt_bsdmd5. The Blowfish module is at crypt_bsdbf.

Developers can create new modules for alternate password-obscuring algorithms. Application developers must use the crypt_gensalt() function instead of manually generating the salt string for passing to the crypt() function.

Modules for alternate algorithms are specified in the crypt.conf(4) file. The module_path field specifies the path to the shared library object that implements the two required functions:

  • crypt_gensalt_impl() – Generates the salt string

  • crypt_genhash_impl() – Generates the encrypted password

For further information, see the crypt(3C) and the policy.conf(4) man pages.

12/02 

New Flags for madvise() Function

The madvise() function enables the kernel to optimize access to a user-defined region of memory. This Solaris release includes three new flags for the madvise() function:

  • MADV_ACCESS_LWP – Gives a specified lightweight process (LWP) resource allocation priority

  • MADV_ACCESS_MANY – Specifies an address range that is intensively used by processes across the machine

  • MADV_ACCESS_DEFAULT – Resets an address range's access pattern to the system default

For further information on the madvise() function, see the madvise(3C) man page.

12/02 

Linkers and Libraries Updates

This Solaris release includes new linker-editor features such as string table compression, unreferenced section elimination, and unreferenced dependency detection. For a complete list of these new features, see “New Linker and Libraries Features and Updates” in the Linker and Libraries Guide.

12/02 

Smartcard Middleware APIs

The Solaris Smartcard framework now provides low-level middleware APIs. These APIs can be used to exchange data with a smart card by using a smart card reader. The APIs can be used in platforms such as the Sun BladeTM and Sun RayTM systems. Applications that are written in the Java language or in C can use these interfaces.

For more information, see the libsmartcard(3LIB) man page and the JavaDocs in /usr/share/javadoc/smartcard.

9/02 

Software Developer Documentation Changes

Description 

Release Date 

New Solaris WBEM Developer's Guide

The new Solaris WBEM Developer's Guide is a combination of the two books on WBEM that were part of earlier Solaris 9 releases: the Solaris WBEM SDK Developer's Guide and the Solaris WBEM Services Administration Guide. This change was made to order sequentially the tasks that are associated with WBEM development and deployment. Other changes are listed here:

  • The chapter on SNMP was removed.

  • The appendix that contains the Solaris schemas now includes two MOF files, WBEMServices.mof and Solaris_DMGT.1.0.mof. The Solaris_VM1.0.mof file was updated to Solaris_VM2.0.mof because two of the providers that were in that MOF file were moved into the Solaris_DMGT.1.0.mof file.

  • In the chapter on “Using the CIM Object Manager,” the steps for upgrading from a previous Solaris release were changed. The change consisted of removing the suggestion to convert existing CIM Object Manager data from the older format that was used in early WBEM releases. Instead, the new suggestion is to recompile all of the MOF files by using the mofcomp command.

  • The introductory chapters from the Solaris WBEM SDK Developer's Guide and the Solaris WBEM Services Administration Guide were merged into a single introductory chapter.

4/03 

New and Revised Documentation in the Solaris 9 4/03 Release

The following revised documentation is available in the Solaris 9 4/03 Update release:  

The following new documentation is available in the Solaris 9 4/03 Update release:  

4/03 

New and Revised Documentation in the Solaris 9 12/02 Release

The following revised documentation is available in the Solaris 9 12/02 Update release:  

The following new documentation is available in the Solaris 9 12/02 Update release:  

12/02