test

ChorusOS 5.0 Transition Guide

Part II Transition Information for Users and System Administrators

This section of the guide indicates changes to file systems, 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

This chapter describes changes to the file system administration in version 5.0 of the ChorusOS operating system. It includes changes to file system and media support.

Changes to File Systems

This section describes changes made to the file systems in ChorusOS 5.0. For more information on file systems and file system administration, refer to the ChorusOS 5.0 System Administrator's Guide.

Changes to Media and File System Support

The following new media and file systems are supported in version 5.0 of the ChorusOS operating system.

SCSI CD-ROM Drive

Version 5.0 of the ChorusOS operating system supports SCSI CD-ROM disk drives. The ChorusOS file system requires that you use special device driver files to read from this device. For more information, see "Special Device Driver Files" in ChorusOS 5.0 System Administrator's Guide and special(7S).

ISO 9660 File System

The ChorusOS operating system now provides support for the ISO 9660 File System on SCSI CD-ROM disk drives.

New NFS Version

ChorusOS 5.0 now supports NFS version 3.0. NFS version 2.0 continues to be supported.

Chapter 4 Configuration Changes

This chapter describes new features and tunables that can be configured in version 5.0 of the ChorusOS operating system. It includes features and tunables whose default values have been changed.

New Features and Tunables

This section describes the new features and tunables added in version 5.0 of the ChorusOS operating system, including the default settings of the features in both configuration environments.

New Features

The following table provides a list of the features added in version 5.0 and their default settings in both the Basic and Extended configuration profiles.

For more information on these features, see "Configuring and Tuning" in the ChorusOS 5.0 System Administrator's Guide.

Table 4-1 New Features and Their Default Settings

Feature 

Basic Profile 

Extended Profile 

BLACKBOX

true 

true 

CORE_DUMP

false 

false 

DEV_CDROM

true 

true 

DEV_DISK

true 

true 

DEV_NVRAM

true 

true 

IOM_DEV_MNGT

true 

true 

IPv6

false 

false 

ISOFS

true 

true 

OS_GAUGES

false 

false 

POSIX_REALTIME_SIGNALS

true 

true 

POSIX_SHM

true 

false 

SOLARIS_SYSEVENT

false 

false 

SYSTEM_DUMP

false 

false 

WDT

false 

false 

Changed Features

The following table lists the features for which the default settings have changed in version 5.0 of the ChorusOS operating system.

Table 4-2 Features for Which the Default Settings Have Changed

Feature 

Basic Profile 

Extended Profile 

ROUND_ROBIN

false 

false 

ON_DEMAND_PAGING

false 

false 

RTMUTEX

false 

false 

SOFTINTR

false 

false 

VTIMER

false 

false 

IPC

true 

true 

IPC_REMOTE

false 

false 

LOCAL_CONSOLE

true 

false 

IOM_IPC

false 

false 

IOM_OSI

false 

false 

SCSI_DISK

false 

false 

FLASH

true 

true 

RAWFLASH

true 

true 

VTTY

false 

false 

FIFOFS

false 

false 

FS_MAPPER

false 

false 

UFS

false 

false 

NFS_SERVER

false 

false 

DYNAMIC_LIB

true 

true 

GZ_FILE

false 

true 

POSIX_MQ

false 

false 

POSIX_SHM

true 

false 

PPP

false 

false 

HOT_RESTART

false 

false 

DEBUG_SYSTEM

true 

true 

New Tunables and Their Default Settings

The following table lists the tunables that are new in version 5.0 of the ChorusOS operating system, along with their default settings.

Table 4-3 New ChorusOS Tunables

Tunable 

Description 

Default Setting 

kern.mkstat.maxevents

Maximum number of MKSTAT events

1024 

kern.systemdump.systemdumpSize

System dump memory area size 

0x20000 

kern.blackbox.maxBufferNumber

Maximum number of circular buffers 

2 

kern.blackbox.bufsize

Size of each blackbox circular buffer (in Kb)

64 

kern.blackbox.maxFilterNumber

Maximum fine-grained filters 

64 

kern.blackbox.maxProcIdNumber

Maximum proc ID filters 

64 

kern.blackbox.kernelLogging

Microkernel logging messages 

0 

iom.persistentramdisk0

Current size of persistent ramdisk 0 

0 

iom.persistentramdisk1

Current size of persistent ramdisk 

0 

iom.persistentramdisk2

Current size of persistent ramdisk 2 

0 

iom.persistentramdisk3

Current size of persistent ramdisk 3 

0 

iom.persistentramdisk4

Current size of persistent ramdisk 4 

0 

iom.persistentramdisk5

Current size of persistent ramdisk 5 

0 

iom.persistentramdisk6

Current size of persistent ramdisk 6 

0 

iom.persistentramdisk7

Current size of persistent ramdisk 7 

0 

iom.persistentramdisk8

Current size of persistent ramdisk 8 

0 

iom.persistentramdisk9

Current size of persistent ramdisk 9 

0 

iom.persistentramdiska

Current size of persistent ramdisk 10 

0 

iom.persistentramdiskb

Current size of persistent ramdisk 11 

0 

iom.persistentramdiskc

Current size of persistent ramdisk 12 

0 

iom.persistentramdiskd

Current size of persistent ramdisk 13 

0 

iom.persistentramdiske

Current size of persistent ramdisk 14 

0 

iom.persistentramdiskf

Current size of persistent ramdisk 15 

0 

iom.wdt.defer

Defer watchdog interrupt processing to C_OS interrupt thread 

0 

iom.wdt.sysdump

watchdog triggering system dump 

0 

iom.wdt.period

Internal period (in ms) of the watchdog timer 

4000 

iom.wdt.slack

Slack time (in ms) of the internal timeout handler 

4000 

iom.wdt.action

Execution time (in ms) of the action taken by the watchdog interrupt handler 

2000 

iom.wdt.maxInterval

Maximum timeout interval (in ms) allowed by the watchdog timer API  

180000 

iom.wdt.startupInterval

Maximum time (in ms) required for the startup sequence to complete 

0 

iom.wdt.shutdownInterval

Maximum time (in ms) required for the shutdown sequence to complete 

0 

iom.os_gauges.activestart

OS_GAUGES signaling sysevents actived at C_OS init 

0 

iom.os_gauges.syslog

OS_GAUGES sysevents errors in syslog messages 

0 

iom.bootverbose

C_OS Activate boot verbose mode 

0 

iom.nprocs

C_OS maximum number of processes 

64 

iom.nthreadsperproc

C_OS maximum number of threads per process 

64 

iom.nprocsperuid

C_OS maximum number of processes per user 

63 

iom.maxcoresize

C_OS maximum permitted size of a core file 

2100000 

iom.maxsockets

C_OS maximum number of open sockets 

64 

iom.nmbufs

C_OS maximum number of open sockets 

2048 

iom.userstacksize

Default stack size of user mode threads 

0x8000 

cgtp.filter_tab_nb

CGTP number of filter tables 

40 

cgtp.sub_tab_nb

CGTP number of subtables in filter tables 

6 

cgtp.entry_nb

CGTP number of entries per subtable 

[2, 4096] by power of 2 

cgtp.elem_nb

CGTP number of elements per entry 

4 

cgtp.resolution

Definition of CGTP filter period 

4 

iom.ipv6.gif.number

Number of GIF interfaces 

1 

iom.inet.use_hw_checksum

Mask controlling the use of hardware checksum capability by the networking stack 

0x001 -- IP header checksum 

0x002 -- TCP header checksum 

0x004 -- UDP header checksum 

0x008 -- checksum over IP fragments 

0x010 -- hardware fragments IP packets 

0x100 -- IP header checksum verified on reception 

0x200 -- IP header checksum is valid 

0x400 -- data checksum computed on reception 

0x800 -- data checksum computed with TCP/UDP pseudo headers 

0xffff 

iom.rtsig.sigqueuemax

Maximum number of signals that can be queued per process 

32 

sysdump.device

Device number used to process the TFTP transfer 

0 

Support for Floating Point Configuration

Version 5.0 of the ChorusOS operating system provides hardware support for floating point configuration. To facilitate this, two new features and one new tunable have been added. The two new features are FPU and FPU_EMUL. The new tunable is kern.exec.dflThreadFpuCtrl.

For the floating point support to be active, set FPU=true and FPU_EMUL=false. Applications should be built with FFPU=ON. With these settings:

Note -

The sysGetConf(2K) system call has been enhanced to retrieve enabled features. The floating point configuration support applies to the PowerPC platform only.

Support for FPU Exception Handling

A new tunable, kern.exec.dflThreadFpuCtrl, has been added to configure default thread behaviour on floating point exceptions. This tunable is a bit field and is the logical OR of MSR(FE0,FE1) bits and FPSCR(24-31) control bits.

The following bits may be set or cleared:

MSR(FE0,FE1)=0x00000000

Floating-point exceptions disabled

MSR(FE0,FE1)=0x00000900

Floating-point precise exception mode

FPSCR(VE)=0x00000080

Invalid operation exception enabled

FPSCR(OE)=0x00000040

Overflow exception enabled

FPSCR(UE)=0x00000020

Underflow exception enabled

FPSCR(ZE)=0x00000010

Zero divide exception enabled

FPSCR(XE)=0x00000008

Inexact operation exception enabled

FPSCR(NI)=0x00000004

Non IEEE mode. This bit should never be set.

FPSCR(RN)=0x00000000

Round to nearest

FPSCR(RN)=0x00000001

Round toward zero

FPSCR(RN)=0x00000002

Round toward +infinity

FPSCR(RN)=0x00000003

Round toward -infinity

MMU/Cache Configuration

To provide MMU/cache configuration, two new tunables have been added:

kern.mem.cacheMode defines how processor caches should be configured. It is a bit field and is the logical OR of the following bit values:

HID0(ICE)=0x00008000

Instruction cache enabled (L1)

HID0(DCE)=0x00004000

Data cache enabled (L1)

L2CR(L2E)=0x80000000

Unified L2 cache enabled

L2CR(L2DO)=0x00400000

For data access only

L2CR(L2IO)=0x00000400

For instruction access only

L2CR(L2WT)=0x00080000

In write-through mode

kern.mem.pgTableSzLog2 defines the memory size to be allocated to the MMU hardware page table (HTAB). To force the HTAB table size to be a power of 2, the tunable value is defined as Log2(size). Thus, 2^kern.mem.pgTableSzLog2 bytes are allocated to the HTAB table. kern.mem.pgTableSzLog2 must be in the value range [16..25].

Note -

This support applies to the PowerPC platform only.

Chapter 5 Networking changes

This chapter describes the ChorusOS networking changes in version 5.0. The chapter includes:

Messaging Changes

The major changes in messaging involve the upgrade of the Sun RPC library from version 4 to version 5. This change has the following implications:

RPC Extensions

The ChorusOS 5.0 operating system extends the RPC library by adding:

Changes to Network Protocols

This section describes the changes made to network protocols.

IPv6

IPv6 is a major enhancement of the Internet Protocol which breaks the IPv4 limitations, particularly the address range limitation. IPv6 also simplifies the IP headers for optimizing implementations.

Note -

IPv6 and IPv4 stacks co-exist in version 5.0 of the ChorusOS operating system.

For more information on support for IPv6, refer to "The ChorusOS system and IP" in the ChorusOS 5.0 System Administrator's Guide.

For a complete guide to migrating from IPv4 to IPv6, refer to "Transitioning From IPv4 to IPv6" in the Solaris System Administration Guide, Volume 3.

Network Time Protocol (NTP)

The new NTP feature provides a set of daemons and commands that enable you to synchronize the dates of different ChorusOS systems. The date is synchronized within a client/server architecture. A ChorusOS system may request the date or provide the date to other systems.

The Network Time Protocol Daemon (ntpd)

The ntpd daemon can run as a server or as a client. The server feature provides a reference clock available to all systems on the network. The client feature is used to compute a clock according to other sources and to keep the system clock synchronized.

The ntpq Command

This command enables you retrieve or to set the ntpd configuration dynamically. For example, the list of reference clocks used by servers for synchronization can be modified dynamically with ntpq

The ntptrace Command

ntptrace determines the source from which a particular NTP server gets its time and follows the chain of NTP servers back to their master time source.

The ntpdate command

ntpdate enables you to retrieve and set the system time using NTP. Requests made by ntpdate are in unicast mode. Although ntpdate is not the best way to request the time periodically, or to maintain a synchronized date (since it is a command) it can be useful when used with a mechanism like a cron tab.

Changes to Network Utilities

This section describes the network utilities that are new in version 5.0 of the ChorusOS operating system.

traceroute

The traceroute utility tracks and prints the route that packets follow to the network host. It uses the IP protocol time to live field and attempts to elicit an ICMP TIME_EXCEEDED response from each gateway along the path to a host.

For more information on the implementation of the traceroute utility, see the traceroute(1M) man page.

tcpdump

The tcpdump utility displays the headers of packets on a network interface that match a specified boolean expression.

For more information on this utility, see the tcpdump(1M) man page.

Enhanced System Security

The introduction of the password management feature to the ChorusOS operating system provides enhanced system security. The password management feature uses the Lightweight Directory Access Protocol (LDAP).

The ldap.conf file contains information about the location of the LDAP server for password management in the ChorusOS operating system. For more information. see the hosts(4CC)ldap.conf(4CC) man page.

Password Management

Version 5.0 of the ChorusOS operating system includes the ability to manage user passwords through its password management feature. Related files are located in /etc/master.passwd and /etc/group. These files enable more flexible security management, in addition to the standard /etc/security file. You can enable the password management feature by running pwd_mkdb(1M).

For more information on the implementation of password management in the ChorusOS operating system, see "System Administration in the Extended Profile" in the ChorusOS 5.0 System Administrator's Guide.

Chapter 6 Changes to Utilities

This chapter describes the new target, host and system management utilities available in version 5.0 of the ChorusOS operating system.

Target Utilities

This section describes the new target utilities in the ChorusOS operating system.

cbfs

The cbfs utility can be used to install and manage a ChorusOS boot file system on a disk drive or a flash device. Disk drives must be labeled with the command disklabel(1M). For more information, see the cbfs(1CC) man page.

Host Utilities

This section describes the new host utilities in the ChorusOS operating system.

Boot Storage Device

The new Boot Storage Device feature provides a service to manage system images stored on a persistent device. The API provides you with extensive information about a system image stored on a device. The Boot Storage Device feature incorporates three utilities - bootMonitor, bootAgent and bootConfig.

bootMonitor

The bootMonitor utility is able to boot the system from a system image on a persistent device or downloaded from the network. bootMonitor uses standard network protocols over an Ethernet line to load and boot the system image. This system image must be an ELF binary. For more information, see the bootMonitor(1M) man page.

bootConfig

While bootMonitor uses boot agents to locate and boot the required system image, bootConfig is used to select the boot agent to be used and to enable the parameters that describe the boot environment to be passed. For more information, see the bootConfig(1M) man page.

bootAgent

The bootAgent is a modular piece of code that groups together certain protocols or drivers and a parameter interpreter used by bootMonitor. The bootAgent is executed by the bootMonitor according to the bootConfig.

rdbd

The new rdbd host utility allows the GDB debugging tool for ChorusOS systems to debug application core dumps. rdbd is similar to rdbc(1CC), the remote debugging daemon, except that rdbd runs on the host, while rdbc runs on a target. For more information, see the rdbd(1CC) man page.

rpcbind

rpcbind rpcbind is a server that converts RPC program numbers into universal addresses. It must be running on the host to be able to make RPC calls on a server on that machine. For more information, see the rpcbind(1CC) man page.

System Management Utilities

This section describes the new system management utilities in the ChorusOS operating system.

dhcrelay

The DHCP Relay Agent listens for DHCP requests on all interfaces attached to a host, unless one or more interfaces are specified on the command line, using the -i flag. For more information, see the dhcrelay(1M) man page.

gifconfig

The gifconfig command configures the physical address for the generic IP tunnel interface. See the gifconfig(1M) man page for more information.

logger

logger provides a shell command interface to the syslog(3STDC) system log module. For more information, see the logger(1M) man page.

named

named is the Internet domain name server. Without any arguments, named will read the default configuration file /etc/named.conf, read any initial data, and listen for queries. For more information, see the named(1M) man page.

named-xfer

named-xfer is an ancillary program executed by named(1M) to perform an inbound zone transfer. For more information, see the named-xfer(1M) man page.

ndp

The ndp command manipulates the address mapping table used by the Neighbor Discovery Protocol (NDP). For more information, see the ndp(1M) man page.

passwd

The passwd command changes the user's local, Kerberos, or NIS password. For more information, see the passwd(1M) man page.

pdump

The C_INIT(1M) built-in command, pdump, dumps a core image of a specified process as an ELF format file. See the pdump(1M) man page for more information.

ping6

The ping6 command uses the ICMPv6 protocol's mandatory ICMP6_ECHO_REQUEST datagram to elicit an ICMP6_ECHO_REPLY from a host or gateway. See the ping6(1M) man page for more information.

pwd_mkdb

The pwd_mkdb utility creates secure and insecure password databases for a specified file. For more information, see the pwd_mkdb(1M) man page.

rtsold

The rtsold daemon sends ICMPv6 router solicitation messages on specified interfaces. For more information, see the rtsold(1M) man page.

sync

The sync command executes the sync system primitive. If the system is to be stopped, sync must be called to ensure file system integrity. For more information, see the sync(1M) man page.

syslogd

The syslogd daemon reads and logs messages to the system console, log files, other machines or users as specified by its configuration file. See the syslogd(1M) man page for more information.

tftpd

The tftpd deamon is a server supporting the Internet Trivial File Transfer Protocol. For more information, see the tftpd(1M) man page.