ChorusOS 5.0 System Administrator's Guide

Configuration Options

Configuring a ChorusOS operating system means defining all the components, and their characteristics, that are assembled to form a system image. There are several types of configuration options:

Configuration settings, including the configuration profile definitions are stored in the configuration directory, conf, in your system image build area. The configuration directory is read and updated by both the command-line and graphical configuration tools.

Feature Options

A ChorusOS feature is a boolean variable, whose value determines whether or not a particular component is included in the system image. Setting a feature to true results in code being added to the microkernel, providing additional services such as file system handlers, or networking protocols.

Feature options within the ChorusOS operating system are listed in "ChorusOS Operating System Features" in ChorusOS 5.0 Features and Architecture Overview.

Configuration Profiles

The ChorusOS operating system provides two pre-defined configuration profiles, the basic profile and the extended profile, to help you select an initial configuration for the operating system. These profiles include or remove certain features in the system.

The extended profile is the default profile, and does not need to be explicitly specified.

The basic configuration profilecorresponds to a realistic configuration, keeping the footprint small. With this configuration, applications are usually embedded in the system image and launched either at boot time or subsequently from the image file system or the boot file system. This configuration uses the flat memory model, to minimize the footprint.

In the basic profile, application actors are loaded at boot time as part of the system image. These actors are also known as boot actors.

When the system boots, actors included in the system image are loaded. For each actor, a thread is created and starts running at the actor's program entry point.

For instructions on building an application actor, embedding it in the system image and running it in the basic profile, consult the ChorusOS 5.0 Application Developer's Guide.

The extended configuration profile corresponds to a reference configuration for telecommunications systems. It includes support for networking using remote IPC over Ethernet and an NFS client. This uses the protected memory model.

Table 2-1 shows the settings of all the features in the extended and basic configuration profiles.

Table 2-1 Microkernel Feature settings in the extended and basic configuration profiles
 Nameextended profile valuebasic profile value
 Microkernel features
 USER_MODEtruetrue
 ROUND_ROBINtruefalse
  VIRTUAL_ADDRESS_SPACEtruefalse
 ON_DEMAND_PAGING [The ON_DEMAND paging feature is platform-dependent. On platforms that do not support the virtual memory model, this can be hidden, using: configurator -list features.] falsefalse
 MONITORfalsefalse
 SEMtruetrue
 EVENTtruetrue
 RTMUTEXfalsefalse
 SOFTINTRfalsefalse
 TIMERtruetrue
 VTIMERfalsefalse
 DATEtruetrue
 RTCtruetrue
 MKSTATfalsefalse
 PERFtruetrue
 MONtruefalse
 IPCtruetrue
 IPC_REMOTEfalsefalse
 MIPCtruetrue
 LAPBINDtruetrue
 LAPSAFEtruetrue
 LOGtruetrue
 SYSTEM_DUMPfalsefalse
 BLACKBOXtruetrue

Table 2-2 C_INIT Feature Settings and Input Output Manager Feature settings in the extended and basic configuration profiles
 Nameextended profile valuebasic profile value
 C_INIT features
 RSHtruefalse
 LOCAL_CONSOLEfalsetrue
 Input Output Manager features
 IOM_IPCfalsefalse
 IOM_OSIfalsefalse
 DEV_MEMtruefalse
 DEV_CDROMtruetrue
 DEV_DISKtruetrue
 DEV_NVRAMtruetrue
 RAM_DISKtruetrue
 SCSI_DISKfalsefalse
 FLASHtruetrue
 RAWFLASHtruetrue
 OS_GAUGESfalsefalse
 VTTYfalsefalse
 WDTfalsefalse
 FIFOFStruefalse
 FS_MAPPERfalsefalse
 MSDOSFStruetrue
 UFSfalsefalse
 ISOFStruetrue
 NFS_CLIENTtruefalse
 NFS_SERVERfalsefalse
 ACTOR_SRCDBGtruetrue
 GZ_FILEtruefalse
 CORE_DUMPfalsefalse
 IOM_DEV_MNGTtruetrue
 POSIX_MQfalsefalse
 POSIX_SHMtruefalse
 AF_LOCALtruetrue
 BPFtruefalse
 POSIX_SOCKETStruetrue
 PPPfalsefalse
 SLIPfalsefalse
 IPv6falsefalse
 POSIX_REALTIME_SIGNALStruetrue
 SOLARIS_SYSEVENTfalsefalse
 HOT_RESTARTfalsefalse
 DRV_MERGEfalsefalse
 DEBUG_SYSTEMtruetrue
 EDB_MONITORfalsefalse


Note -

The MONITOR feature is an internal feature used only by the C Virtual Machine, (CVM), a compact Java Virtual Machine.


Both configuration profiles include support for system debugging.

You can use one of these configuration profiles as the initial configuration for your system, and add or remove specific feature options using the configurator utility (see "Command-line Configuration Tool"). Once you have created your initial configuration, you can also use the graphical configuration tool ews (see "The Embedded Workshop Graphical Configuration Tool") to manage the configuration.

Tunable Parameters

Tunable parameters are system parameters which affect system behavior and capabilities. They are used to configure the microkernel and the included features, to change their behavior, and adapt them to your needs. Typical examples of tunables are: maximum number of microkernel objects, scheduler type and attributes for threads, or system clock frequency. Each system component or feature adds a number of these tunable parameters.

Static Parameters

Static parameters are tunable parameters whose values are set permanently within a system image. Changing these values requires rebuilding the system image.

The procedure for assigning new values to tunable parameters is detailed in "Changing Tunable Parameter Values".

Dynamic Parameters

For some tunable parameters, an additional flexibility is offered: the ability to assign values to these parameters at various stages of system production and execution. These types of parameters are called dynamic parameters. These dynamic parameters define the system environment. A basic set of services allows this environment to be constructed and consulted within a system image, at boot time and runtime.

Compared to static parameters, dynamic parameters require additional target data memory in order to store their names and values.

The procedure for modifying dynamic parameters is detailed in "Modifying the System Environment".

System Image Components

The system image contains a configured version of the ChorusOS operating system, and possibly some user-defined applications (actors).

Depending on its configuration options, the ChorusOS operating system is built from a microkernel and a collection of actors. These actors, which contribute to the implementation of some ChorusOS operating system features and system image components are called ChorusOS operating system actors.

Configuration options concerning the system image components or OS actors deal mainly with the inclusion of system and application actors within system images.