ChorusOS 5.0 Transition Guide


The ChorusOS 5.0 Transition Guide provides information about:

This book assumes you are familiar with the ChorusOS operating system and the C programming language.

Who Should Use This Book

This guide will assist users, system administrators and software developers in making the transition from ChorusOS 4.0 to ChorusOS 5.0.

Before You Read This Book

If you are considering migrating your applications or drivers to version 5.0 and you are not familiar with the ChorusOS operating system, you should first read:

How This Book Is Organized

This guide is divided into 4 parts with 12 chapters:

Part I - Upgrading to Version 5.0 of the ChorusOS Operating System

This part of the guide provides an overview of the major enhancements that have been added in version 5.0 and contains transitional information affecting the installation process.

Chapter 1, Overview of Major Enhancements in ChorusOS 5.0 describes the major enhancements to the ChorusOS operating system. This is not a complete list of changes, but an at-a-glance view of areas of the operating system that have been enhanced.

Chapter 2, Changes to the ChorusOS 5.0 Installation suggests things to consider to facilitate a smooth transition through software installation and post-installation.

Part II - Transition Information for Users and System Administrators

This part of the guide indicates changes to file systems, configurables, networking, and host and target utilities. It will assist users in understanding changes to the local computing environment and changes to routine tasks.

Chapter 3, File System Changes describes changes to file system administration, including changes to the file system and media support.

Chapter 4, Configuration Changes describes new features and tunables that can be configured. It includes features and tunables whose default values have changed in this version of the ChorusOS operating system.

Chapter 5, Networking changes describes networking changes, including messaging and protocol changes, and changes to the network utilities.

Chapter 6, Changes to Utilities describes changes to the host, target and system management utilities offered in the ChorusOS operating system.

Part III - Transition Information for Application Developers

This part of the guide focuses on changes that affect developers and the programming environment.

Chapter 7, Additions and Changes to the Programming Environment provides information on changes made to the programming environment, including a description of the new features available to application developers.

Chapter 8, Standard Application Interfaces and POSIX Interfaces describes the changes made to the API organization in version 5.0 of the ChorusOS operating system. It includes a description of the new POSIX support.

Chapter 9, Tool changes discusses changes made to the development tools.

Part IV - Transition Information for BSP Developers

This part of the guide describes the reorganization of the ChorusOS source trees and additional changes relevant to BSP developers.

Chapter 10, Changes to DDIs and DKI Extensions describes the new and changed DDIs and DKIs.

Chapter 11, Changes to Drivers illustrates the changes made to the driver source tree and lists the new and updated drivers for version 5.0 of the ChorusOS operating system.

Chapter 12, Changes to Boot Libraries and Boards lists changes made to the boot libraries and boards.

Related Books

The following books contain additional information about version 5.0 of the ChorusOS operating system that will help you with transition:

Ordering Sun Documents, an Internet professional bookstore, stocks select product documentation from Sun Microsystems, Inc.

For a list of documents and how to order them, visit the Sun Documentation Center on at

Accessing Sun Documentation Online

The docs.sun.comSM Web site enables you to access Sun technical documentation online. You can browse the archive or search for a specific book title or subject. The URL is

Directory Conventions

The following table describes the directory conventions used in this book.

Table P-1 Directory Conventions




Directory containing the ChorusOS 5.0 download files. 




Directory containing sufficient space to extract the delivery. This directory can be a local or an NFS mounted disk that has "write" permission. 




Directory where you install the ChorusOS product. 

Example (also default):


where processor_family is one of the following:

UltraSPARC, x86, PowerPC, MPC8xx

Note that, during installation, you can choose the installation directory other than /opt/SUNWconn/SEW/. However, the 5.0-processor_family directory containing the ChorusOS directories and files is automatically created in the directory you specify.


Directory where you configure and build the system image. This directory can be a local or an NFS mounted disk, but you must have "write" permission. 




Directory containing the ChorusOS file system.  




Directory on the host containing a file system you want to mount on a target. 




Directory containing the source files. 



Note -

family is one of the following:

Typographic Conventions

The following table describes the typographic changes used in this book.

Table P-2 Typographic Conventions

Typeface or Symbol 




 The names of commands, files, and directories; on-screen computer output

Edit your .login file.

Use ls -a to list all files.

machine_name% you have mail.


 What you type, contrasted with on-screen computer output

machine_name% su



 Command-line placeholder: replace with a real name or value

To delete a file, type rm filename.


Book titles, new words, or terms, or words to be emphasized. 

Read Chapter 6 in User's Guide.

These are called class options.

You must be root to do this.

Shell Prompts in Command Examples

The following table shows the default system prompt and superuser prompt for the C shell, Bourne shell, and Korn shell.

Table P-3 Shell Prompts



 C shell promptmachine_name%
 C shell superuser promptmachine_name#
 Bourne shell and Korn shell prompt$
 Bourne shell and Korn shell superuser prompt#