The configurator utility provides an option to display the C5 operating system configuration in a web browser in HTML. Within your build directory, type the following command:

$ configurator -display /tmp/ChorusOS.html 

You can then use your browser to navigate through the ChorusOS.html file generated by this command.

Figure 2.1. Microkernel Configuration Displayed in HTML

Two predefined profiles are provided, as described in Section 2.2, “Configuration Files”. To select the basic profile, type:

% configurator -p conf/basic

To re-select the extended (default) profile, type:

% configurator -p conf/extended

You can use the configurator utility to add, remove, or list a feature.

% configurator -set 
feature_name=true

% configurator -set EVENT=true

2.3.3.2. Removing a Feature

To remove a feature, type:

% configurator -set feature_name=false

The status of the feature_name is set to false.

For example, to remove the EVENT feature:

% configurator -set EVENT=false

You can reset the value of a feature to the default as follows:

% configurator -reset EVENT

	Note
	The reset command resets the value to the extended profile default.

% configurator -list features 
feature_name 

% configurator -list features

SEM:bool='true'
EVENT:bool='true'
RTMUTEX:bool='false'
TIMER:bool='true'
VTIMER:bool='false'
DATE:bool='true'

% configurator -info features 
feature_name 

% configurator -info features NFS_SERVER


NFS_SERVER:bool='false'
Possible values: true|false
Description: NFS server access from target machine

Tunable parameters are defined by symbolic names within the C5 operating system components. Symbolic names include dots (.), to maintain compatibility with previous releases of the C5 operating system. An example of a symbolic name is kern.exec.maxCpuNumber, which is a tunable.

The definition of a tunable parameter includes the definition of a default value for this parameter. Integer values of tunable parameters are expressed either as integers or as hexadecimal numbers.

To change the value of a tunable parameter, use:

% configurator -set 
tunable_name=value

For example, to reconfigure the microkernel to enable the creation of 300 threads:

% configurator -set kern.exec.maxThreadNumber=300

You can check the value of a tunable parameter as follows:

% configurator -list tunable 
tunable_name

You can list the values of all the microkernel executable tunables as follows:

% configurator -list tunable kern.exec.*

The output lists the microkernel executable tunables and their values:

kern.exec.maxCpuNumber:int='1'
kern.exec.maxActorNumber:int='64'
kern.exec.maxThreadNumber:int='300'
kern.exec.bgStackSiz:int='0x1000'
kern.exec.dflSysStackSize:int='0x3000'
kern.exec.dflUsrStackSize:int='0x4000'
kern.exec.dblFltStackSize:int='0x800'
kern.exec.intrStackSize:int='0x3000'

You can list a tunable parameter in greater detail with the -info option:

% configurator -info tunable 
tunable_name 

The tunable, its value and its description are displayed:

% configurator -info tunable kern.lap.*


kern.lap.maxLapBindNumber:int='256'
Description: Maximum number of bind LAPs 

kern.lap.maxLapSafeNumber:int='128'
Description: Maximum number of safe LAPs

The system environment is defined by a set of dynamic parameters. The system environment is a set of name-value pairs, where name and value are character strings. Values for system environment variables can be obtained by the system and applications at runtime using the sysGetEnv(2K) system call.

To display all the system environment variables, type:

% configurator -list env

To set a new environment variable, or change its value:

% configurator -setenv 
envar=value

Here is an example:

% configurator -setenv MESSAGE='HelloWorld'
  

To unset a variable, so that it is removed from the environment, type:

% configurator -resetenv 
envar

After you have finished modifying the configuration, rebuild the system image by typing:

% make chorus