ChorusOS 4.0 x86/Pentium Target Family Guide

This guide describes how to run the ChorusOS^TM 4.0 product for the x86/Pentium processor family.

Preface

How This Guide is Organized

ChorusOS 4.0 x86/Pentium specific information is provided in the following major sections:

"Development Environment", includes supported hosts, host operating systems and development systems.
"ChorusOS 4.0 Supported Features", includes kernel components and POSIX components.
"Libraries".
"Utilities", includes host and target utilities.
"Reference Hardware", includes supported reference platforms, supported devices, and validated reference platforms.
"How to Build and Boot a System Image on the Target".
Appendix A, ChorusOS 4.0 for x86/Pentium Product Packages and Part Numbers, details the list of Solaris packages in the product components, and the associated part numbers.

Related Books

See the ChorusOS 4.0 Installation Guide for Solaris Hosts for a description of the installation process of the ChorusOS 4.0 product on a host workstation running the Solaris^TM operating environment. This document also describes how to set up a boot server running the Solaris operating environment.

See the ChorusOS 4.0 Introduction for a complete description of the ChorusOS 4.0 features.

Typographical Conventions

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

Table 1-1 Typographical Conventions


Typeface or Symbol	Meaning	Example
`AaBbCc123`	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.`
`AaBbCc123`	What you type, contrasted with on-screen computer output	`machine_name%` `su` `Password:`
`AaBbCc123`	Command-line placeholder: replace with a real name or value	To delete a file, type `rm` `filename`.
AaBbCc123	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

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

Table 1-2 Shell Prompts


Shell	Prompt
C shell prompt	`machine_name%`
C shell superuser prompt	`machine_name#`
Bourne shell and Korn shell prompt	`$`
Bourne shell and Korn shell superuser prompt	`#`

Ordering Sun Documents

Fatbrain.com, an Internet professional bookstore, stocks selected product documentation from Sun Microsystems, Inc.

For a list of documents and how to order them, visit the Sun Documentation Center on Fatbrain.com at http://www1.fatbrain.com/documentation/sun.

Accessing Sun Documentation Online

The docs.sun.com^SM Web site enables you to access Sun technical documentation online. You can browse the docs.sun.com archive or search for a specific book title or subject. The URL is http://www.oracle.com/technetwork/indexes/documentation/index.html.

Obtaining Technical Support

Sun Support Access offerings are available exclusively to members of the Sun Developer Connection Program. To get free membership in the Sun Developer Connection Program, go to http://www.sun.com/developers. For more information or to purchase Sun Support Access offerings, visit: http://www.sun.com/developers/support or contact the Sun Developer Connection Program office near you.

Development Environment

The ChorusOS 4.0 product provides a host-target development environment. Applications are developed on a workstation (the host), and then downloaded and executed on a specific board (the target).

A cross development system is needed to build the applications that execute on the target board (see Section "Utilities").

SPARC^TM/Solaris^TM Reference Host Environments

Prerequisites for the Solaris host reference configuration are the following:

Sun SPARCstation^TM
Solaris 2.6, or Solaris 7
JDK^TM 1.1.3 to 1.1.8, for the installation tool
JDK 1.2, for the graphical configuration tool

Cross Compiler

This development environment component is bundled with the ChorusOS 4.0 for x86/Pentium product:

Chorus Cross Development System 5.0, target PowerPC ELF

The Chorus Cross Development System is based on the Experimental GNU Compiler System egcs 1.1.2 and binutils 2.9.1 and additional patches.

Graphical Debugger

This development environment component is bundled with the ChorusOS 4.0 for x86/Pentium product:

XRAY Debugger from Mentor Graphics, target PowerPC ELF version 4.4crb and additional patches.

ChorusOS 4.0 Supported Features

The following table shows the ChorusOS kernel and operating system optional features that are available for the x86/Pentium processor family. The availability status of a feature, can be one of:

Y

The feature is supported, and is configurable with the configurator(1CC) command, or with the ews GUI configuration tool.

Please refer to the note at the end of the table for information about specific conditions, or restrictions, for a given supported feature.

Some of the features (such as MSDOSFS, FLASH, FS_MAPPER, for example) require specific low-level drivers. These features operate only on platforms which provide these drivers.

N

The feature is not supported.

Feature Description		Feature Name	Availability
Actor management
	Dynamic actor loading management	ACTOR_EXTENDED_MNGT	Y
	User-mode extension support	USER_MODE	Y
	Dynamic libraries	DYNAMIC_LIB	Y
	Compressed file management	GZ_FILE	Y
Scheduling
	POSIX round-robin scheduling class	ROUND_ROBIN	Y
Memory management
	Virtual (user and supervisor) address space	VIRTUAL_ADDRESS_SPACE	Y
	On-demand paging	ON_DEMAND_PAGING	Y
Hot restart and persistent memory
	Hot restart	HOT_RESTART	Y
Inter-thread communication
	Semaphores	SEM	Y
	Event flag sets	EVENT	Y
	Mutual exclusion lock supporting thread priority inversion avoidance	RTMUTEX	Y [RTMUTEX is not supported for Intel 386. It is available for the other supported processors.]
Time management
	Periodic timers	TIMER	Y
	Thread and actor virtual timer	VTIMER	Y
	Date and time of day	DATE	Y
	Real-time clock	RTC	Y
Inter-process communication
	Location-transparent inter-process communication	IPC	Y
	Remote (inter-site) IPC support	IPC_REMOTE	Y
	Remote IPC communications medium	IPC_REMOTE_COMM	Y
	Mailbox-based communications mechanism	MIPC	Y
	POSIX 1003.1-compliant message queues	POSIX_MQ	Y
	POSIX 1003.1-compliant shared memory objects	POSIX_SHM	Y
LAP
	Local name server for LAP binding	LAPBIND	Y
	LAP validity-check option	LAPSAFE	Y
Tools support
	Message logging	LOG	Y
	Profiling and benchmark support	PERF	Y
	System Monitoring	MON	Y
	System debugging	DEBUG_SYSTEM	Y [A flashed system image configured with DEBUG_SYSTEM enabled does not boot. The DEBUG_SYSTEM feature must be disabled.]
C_INIT
	Basic command interpreter on target	LOCAL_CONSOLE	Y
	Remote shell	RSH	Y
File system options
	Named pipes	FIFOFS	Y
	MS-DOS file system	MSDOSFS	Y
	NFS client	NFS_CLIENT	Y
	NFS server	NFS_SERVER	Y
	UFS file system	UFS	Y
I/O management
	Network packet filter	BPF	Y
	Swap support	FS_MAPPER	Y
	Driver for IDE disk	IDE_DISK	Y
	`/dev/mem`, `/dev/kmem, /dev/null`, `/dev/zero`	DEV_MEM	Y
	Support for RAM disk	RAM_DISK	Y
	Support for FLASH media	FLASH	Y
	Virtual TTY	VTTY	Y
	Driver for SCSI disk	SCSI_DISK	Y
	Support for IPC	IOM_IPC	Y
	Support for OSI	IOM_OSI	Y
Networking
	Serial link IP	SLIP	Y
	POSIX 1003.1g-compliant sockets	POSIX_SOCKETS	Y
	Point-to-point protocols	PPP	Y
	Local sockets and pipes	AF_LOCAL	Y
Administration
	ChorusOS statistics	ADMIN_CHORUSSTAT	Y
	`ifconfig` administration command	ADMIN_IFCONFIG	Y
	`mount` administration command	ADMIN_MOUNT	Y
	`rarp` administration command	ADMIN_RARP	Y
	`route` administration command	ADMIN_ROUTE	Y
	`shutdown` administration command	ADMIN_SHUTDOWN	Y
	`netstat` administration command	ADMIN_NETSTAT	Y

Libraries

The ChorusOS operating system provides the elementary libraries indicated in the following list:

ChorusOS embedded library [The `libebd.a`, `libcx.a`, `libm.a` and `libC.a` libraries have been made thread-safe in order to support multithreaded actors.]	`libebd.a`
ChorusOS extended library	`libcx.a`
C++ library	`libC.a`
X11 related client libraries (not thread safe)	`libX11.a`, `libXaw.a`, `libXext.a`, `libXmu.a`, `libXt.a`
Specific BSD APIs (not thread safe)	`libbsd.a`
The SunRPC library	`librpc.a`
The mathematical library	`libm.a`
The ``embedded'' C library [Included in `libebd.a`]	`stdc.a`
The microkernel ``visu'' library [This library is provided for the sake of backwards compatibility only. It is not documented. Its use is strongly discouraged.]	`visu.a`

Utilities

Target Utilities

The following utilities may be run on the target ChorusOS operating system:

chorusStat(1CC)
cp(1CC)
cs(1CC)
date(1CC)
dd(1CC)
df(1CC)
domainname(1CC)
ftp(1CC)
hostname(1CC)
ls(1CC)
mkdir(1CC)
mkfifo(1CC)
mv(1CC)
netstat(1CC)
nfsstat(1CC)
pax(1CC)
PROF(1CC)
profctl(1CC)
rdbc(1CC)
rm(1CC)
rmdir(1CC)
touch(1CC)
uname(1CC)
ypcat(1CC)
ypmatch(1CC)
ypwhich(1CC)
arp(1M)
chat(1M)
chorusNS(1M)
chorusNSinet(1M)
chorusNSsite(1M)
dhclient(1M)
disklabel(1M)
flashdefrag(1M)
format(1M)
fsck(1M)
fsck_dos(1M)
ftpd(1M)
inetNS(1M)
inetNSdns(1M)
inetNShost(1M)
inetNSien116(1M)
inetNSnis(1M)
mkfd(1M)
mkfs(1M)
mount(1M)
mount_msdos(1M)
mount_nfs(1M)
mountd(1M)
newfs(1M)
newfs_dos(1M)
nfsd(1M)
portmap(1M)
shutdown(1M)
slattach(1M)
syncd(1M)
sysctl(1M)
telnetd(1M)
umount(1M)
ypbind(1M)

Host Utilities

The following utilities may be run on the host machine:

chadmin(1CC)
chconsole(1CC)
chlog(1CC)
chls(1CC)
ChorusOSMkMf(1CC)
chserver(1CC)
configurator(1CC)
configure(1CC)
ews(1CC)
mkmerge(1CC)
rdbs(1CC)
profrpg(1CC)

Reference Hardware

ChorusOS 4.0 targets are described in this section from three different points of view:

Reference Processors and BSPs:: This subsection describes the processors on which the ChorusOS 4.0 product can run as well as the details of the BSPs included in the delivery
Reference Target Platforms:: This section describes all the target platforms which can be used as references in the context of Sun support contracts
Validated Reference Targets:: This section describes the precise platforms used to run the Sun QA tests; this may be useful, in case of bugs, as a hint or guide to help in identifying issues which are closely hardware related.

Reference Processors and BSPs

The ChorusOS 4.0 system for x86/Pentium supports the following processors:

Intel 386 (no software FPU emulation)
Intel 486
Intel Pentiums
Intel Celeron

The ChorusOS 4.0 system for x86/Pentium supports the following reference BSPs:

i386at Reference BSP

i386at Reference BSP

Systems

The i386at reference BSP supports standard PC-AT boards.

Devices

The i386at reference BSP supports the following on board devices:

Device Id	ChorusOS Driver
/pci (PCI bridge)	sun:x86-generic-(bus,pci)
/pci/pci-isa (ISA bridge)	sun:pci-generic-(bus,isa)
/pci/pci-isa/i8254 (TIMER)	sun:bus-i8254-timer
/pci/pci-isa/mc146818 (RTC, TIMER)	sun:bus-mc146818-(rtc,timer)
/pci/pci-isa/ns16550-1 (UART)	sun:bus-ns16550-uart
/pci/pci-isa/ns16550-2 (UART)	sun:bus-ns16550-uart
/pci/pci-isa/generic-ide: (IDE disk)	sun:bus-generic-ide
/pci/pci-isa/generic-ide: (IDE other)	not supported
/pci/pci-isa/fdd (floppy)	not supported
/pci/pci-isa/kbd (keyboard)	not supported
/pci/pci-isa/lpt (parallel)	not supported
/pci/pci-isa/mouse (mouse)	not supported

The i386at reference BSP supports the following expansion devices:

Device Id	ChorusOS Driver	Reference Device
/pci/epic100 (ETHER)	sun:pci-epic100-ether	SMC EtherPowerII 10/100 TP
/pci/dec21140 (ETHER)	sun:pci-dec21x4x-ether	ZNYX ZX345 Fast Ethernet
/pci/ne2000 (ETHER)	sun:bus-ne2000-ether	Kingston KNE2000TLC Novell NE2000 plus
/pci/ncr53c825 (SCSI HBA)	sun:pci-ncr53c8xx-scsi_hba sun:scsi_hba-generic-scsi	Symbios Logic SYM8750SP
/pci/ncr53c825/disk@t,l (SCSI disks) where t is the SCSI TARGET number where l is the LUN number	sun:scsi-disk-BSD
/pci/ncr53c825/xxx (SCSI other)	not supported
/pci/pci-isa/smc1660 (ETHER)	sun:isa-smc1660-ether	SMC EtherCard Elite Ultra 16 bits
		SMC EtherCard EZ
/pci/pci-isa/el3 (ETHER)	sun:bus-el3-ether	3Com EtherlinkIII 3C509B
/pci/pci-isa/ne2000 (ETHER)	sun:bus-ne2000-ether
/flash (FLASH memory)	not supported

Reference Target Platforms

This section describes all the target platforms which can be used as references in the context of Sun support contracts.

PC Compatible

Type:: Generic Computer
Processors:: i486/Pentiums/Celeron (33-400 Mhz)
Main memory:: 16-256 MB
L2 cache:: 256-512 KB
Bus bridges:: Processor to PCI, PCI to ISA
Devices:: Asynchronous serial ports (38.4 Kbaud), 10/100BaseT Ethernet (PCI: SMC EtherPowerII, compatible NE2000, ZNYX ZX345; ISA: SMC EtherCard Elite Ultra 16bits/EZ, compatible NE2000, 3Com EtherLinkIII), IDE disk, Ultra-Wide SCSI (PCI: Symbios logic SYM8750SP), Real-time clock, Timers
Firmware:: PC BIOS

Validated Reference Targets

This section describes the precise platforms used to run the Sun QA tests.

Pentium II 300 Mhz/ 64 MB / 512 KB L2 cache / EtherPower II
Celeron 400 Mhz / 128 MB / 128 KB L2 cache / EtherPowerII

How to Build and Boot a System Image on the Target

The procedures below concern x86/Pentium target systems.

Note -

The x86/Pentium configuration for this release differs from that used in previous versions.

Read the procedures below carefully.

Building a ChorusOS System Image

The following procedure assumes that the ChorusOS 4.0 product has already been correctly installed on the host workstation. See the ChorusOS 4.0 Installation Guide for Solaris Hosts for instructions.

Create and change to a build directory where you will build system images:
$ mkdir build_dir $ cd build_dir

Set an environment variable to use with the configure(1CC) command as a shortcut to the base directory.

For example:

Set the environment variable...

To the family-specific product directory. The default value is...

DIR

/opt/SUNWconn/SEW/4.0/chorus-x86

Make sure your PATH has been set correctly to include the directory install_dir/4.0/chorus-x86/tools/host/bin, where the default install_dir is /opt/SUNWconn/SEW. Also make sure that your PATH includes /usr/openwin/bin, which contains the imake utility.

Set the environment variable...	To the family-specific product directory. The default value is...
`DIR`	/opt/SUNWconn/SEW/4.0/chorus-x86

Configure the build directory, using the configure(1CC) command:

If you are building from a binary distribution:

$ configure -b $DIR/kernel \ 
$DIR/os \ 
$DIR/tools \ 
-s $DIR/src/nucleus/bsp/drv \ 
$DIR/src/nucleus/bsp/x86 \ 
$DIR/src/nucleus/bsp/x86/i386at \ 
$DIR/src/iom

Note -

The above command configures the build directory to include components installed during a "Default Install". It does not include optional components, such as the X library or code examples, that you may choose to install separately on Solaris host workstations. For example, in order to include everything in your build environment:

$ configure -b $DIR/kernel \ 
$DIR/os \ 
$DIR/opt/X11 \ 
$DIR/opt/jvm \ 
$DIR/tools \ 
-s $DIR/src/nucleus/bsp/drv \ 
$DIR/src/nucleus/bsp/x86 \ 
$DIR/src/nucleus/bsp/x86/i386at \ 
$DIR/src/iom \ 
$DIR/src/opt/examples

If you are building from the source distribution, see the ChorusOS 4.0 Production Guide.

As a result of configuration, build_dir now contains a Makefile, which is used to generate the build environment, and a Paths file, which specifies paths to files required by and created in the build environment.

Generate the build environment:
$ make

Build a system image:
$ make chorus
The resulting system image file is located in the build directory, build_dir and is called chorus.bmon.

Note -
You can also make a smaller system image that includes only the operating system kernel:
$ make kernonly

Placing the System Image on the Boot Server

See the ChorusOS 4.0 Installation Guide for Solaris Hosts for instructions on how to configure the boot server.

Copy the system image to the boot server.

For example, on a Solaris host workstation:
$ rcp chorus.bmon boot_server:/tftpboot

Verify that everyone has at least read access to the system image on the boot server.

For example:

$ rlogin boot_server
Password: password_for_user
$ ls -l /tftpboot/chorus.bmon
-rwxr-xr-x   1 user    group     1613824 Dec 15 17:33 chorus.bmon*

While logged in to the boot server, create a configuration file for the target.

For a target system with IP address 129.157.197.88 using a boot server with IP address 129.157.197.144, the configuration file contains the following:
```
AUTOBOOT=YES
BOOTFILE=chorus.bmon
BOOTSERVER=129.157.197.144
```
The configuration file is named /tftpboot/819DC558.ChorusOS.4.0, which is constructed from the target system IP address 129.157.197.88 as a concatenation of the following:
- 129 in decimal translates to 81 in hexadecimal
- 157 in decimal translates to 9D in hexadecimal
- 197 in decimal translates to C5 in hexadecimal
- 88 in decimal translates to 58 in hexadecimal
- (optional) .ChorusOS.4.0 identifies the release, and is appended to the concatenation of the IP address expressed in hexadecimal.
Note -
The system first attempts to find the configuration file with the .ChorusOS.4.0 extension. If it fails to find one, however, it attempts to find a configuration file without the .ChorusOS.4.0 extension.

Creating a `bootMonitor` Diskette

See bootMonitor(1CC) for details about how bootMonitor works.

Create a build directory where you will build a bootMonitor image:
$ mkdir bootmon $ cd bootmon
Note that this build directory is different from the directory where you build system images.

Configure the bootMonitor build directory based on the binary distribution:

$ configure -b $DIR/kernel \ 
$DIR/os \ 
$DIR/tools \ 
-s $DIR/src/nucleus/bsp/drv \ 
$DIR/src/nucleus/bsp/x86 \ 
$DIR/src/nucleus/bsp/x86/i386at \ 
$DIR/src/iom

Generate the build environment:
$ make

Edit the special bootmon/conf/mini profile so that it reads:

#
#	Mini Profile
#

#
#	Kernel features
#
-set USER_MODE=false
-set VIRTUAL_ADDRESS_SPACE=false
-set SEM=false
-set EVENT=false
-set MONITOR=false
-set TIMER=false
-set DATE=false
-set RTC=false
-set PERF=false
-set IPC=false
-set MIPC=false
-set LAPBIND=true # Change this from 'false' to 'true'
-set LAPSAFE=true # Change this from 'false' to 'true'
-set MON=false
-set LOG=false

Configure the build environment for bootMonitor:

$ configurator -p conf/mini
$ configurator -set LOADER=lilo

(Optional) Configure the build environment for any ISA Ethernet adapters on the target system.

If you have only PCI Ethernet adapters, you can skip this step.

ISA adapters require that you provide configuration information by setting an ETHER_id environment variable in the system image configuration with a command of the form:
```
configurator -setenv ETHER_id=name,irq,io_base[[,mem_base]]
```
The parameters are as follows:

id

A decimal value ranging from 0 to 9.

Up to ten ISA Ethernet adapters can be declared using ETHER_0, ETHER_1, ..., ETHER_9.

name

The type of the device: EL3, NE2000 or SMC.

irq

A decimal value representing the interrupt request level on the ISA bus.

io_base

A hexadecimal value representing the base for I/O ports, such as 0x300.

mem_base

A hexadecimal value representing the base for shared memory, such as 0xD0000

The memory base parameter is required for SMC Ethernet adapters only.

For example, the following command configures the build environment for one SMC Ethernet adapter with IRQ 9, I/O base at 0x240 and memory base at 0xD0000:
$ configurator -setenv ETHER_0=SMC,9,0x240,0xD0000
The following command configures the build environment for a system with both an NE2000 adapter and an EL3 adapter:
$ configurator -setenv ETHER_0=NE2000,5,0x300 $ configurator -setenv ETHER_1=EL3,7,0x300

Build a bootMonitor image:
$ make bootMonitor
The resulting system image file is located in the build directory, bootmon and is called bootMonitor.image.

Copy the bootMonitor image to a diskette:

$ su
Password: root_password
# /etc/init.d/volmgt stop
# fdformat -v /dev/fd0
Formatting 1.44 MB in /dev/rfd0
Press return to start formatting floppy.
................................................................................
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
# cp bootMonitor.image /dev/fd0
# /etc/init.d/volmgt start
volume management starting.
# eject
/vol/dev/rdiskette0/unlabeled can now be manually ejected
# exit

How to Boot the Target System Using a `bootMonitor` Diskette

Shut down the system.

Connect a serial line from the first serial line port on the target system to the host workstation in order to view console output.

You can use a terminal-type serial cable, where wires 2 and 3 are crossed and 7 (the ground) is straight. However, a serial cable in which all wires are parallel will not work.

Add a line to the host workstation /etc/remote file to make it possible to connect through the serial line using the tip(1) utility. For example:
```
target_hostname:dv=/dev/cua/a:br#9600
```

Connect to the target system using the tip(1) utility:
$ tip target_hostname connected

Place the bootMonitor diskette in the drive.

Reboot, making sure the BIOS causes the system to boot first from the diskette.

If the system boots correctly, messages similar to the following are displayed on the console in the terminal where you issued the tip(1) command:

DebugAgent: trying to sync with DebugServer... 
RAM size: 0x8000000 bytes

ChorusOS r4.0.0 for Intel x86 - Intel x86 PC/AT
Copyright (c) 1999 Sun Microsystems, Inc. All rights reserved.
 
Kernel modules : CORE SCHED_FIFO MEM_FLM KDB TICK ENV LAPSAFE MUTEX PERF \ 
TIMEOUT LAPBIND DKI 
/pci/i8259: sun:pci-i8259-pic driver started
/pci: sun:x86-bios-(bus,pci) driver started
/pci/pci8086,7190@0,0: device node is created by sun:pci-enumerator-
/pci/pci8086,7191@1,0: device node is created by sun:pci-enumerator-
/pci/pci8086,7110@4,0: device node is created by sun:pci-enumerator-
/pci/pci8086,7111@4,1: device node is created by sun:pci-enumerator-
/pci/pci8086,7112@4,2: device node is created by sun:pci-enumerator-
/pci/pci8086,7113@4,3: device node is created by sun:pci-enumerator-
/pci/pci10b8,5@a,0: device node is created by sun:pci-enumerator-
/pci/pci-isa: sun:pci-bios-(bus,isa) driver started
/pci/pci-isa/i8254: sun:bus-i8254-timer driver started
/pci/pci10b8,5@a,0: sun:pci-epic100-ether device started
/pci/pci10b8,5@a,0: Ethernet Address 00:e0:29:3c:6c:7f

Boot Monitor Loader (v1.0)

Searching for adapters...
Unit: 0  device name: pci10b8,5@a,0

Using unit 0

My IP 129.157.197.88, RARP Server IP 129.157.197.144

Loading file 819DC558.ChorusOS.4.0 on server 129.157.197.144: loaded!

Loading file chorus.bmon on server 129.157.197.144: loaded!

Booting downloaded file.

Boot new image ...
DebugAgent: trying to sync with DebugServer... 
RAM size: 0x8000000 bytes

ChorusOS r4.0.0 for Intel x86 - Intel x86 PC/AT
Copyright (c) 1999 Sun Microsystems, Inc. All rights reserved.
 
Kernel modules : CORE SCHED_FIFO SEM MIPC IPC_L MEM_PRM KDB TICK MON ENV \
ETIMER LOG LAPSAFE MUTEX EVENT UI DATE PERF TIMEOUT LAPBIND DKI 
MEM: memory device 'sys_bank' vaddr 0x7bc43000 size 0x189000
/pci/i8259: sun:pci-i8259-pic driver started
/pci: sun:x86-bios-(bus,pci) driver started
/pci/pci8086,7190@0,0: device node is created by sun:pci-enumerator-
/pci/pci8086,7191@1,0: device node is created by sun:pci-enumerator-
/pci/pci8086,7110@4,0: device node is created by sun:pci-enumerator-
/pci/pci8086,7111@4,1: device node is created by sun:pci-enumerator-
/pci/pci8086,7112@4,2: device node is created by sun:pci-enumerator-
/pci/pci8086,7113@4,3: device node is created by sun:pci-enumerator-
/pci/pci10b8,5@a,0: device node is created by sun:pci-enumerator-
/pci/pci-isa: sun:pci-bios-(bus,isa) driver started
/pci/pci-isa/i8254: sun:bus-i8254-timer driver started
/pci/pci-isa/mc146818: sun:bus-mc146818-(rtc,timer) driver started
/pci/pci-isa/ns16550-2: sun:bus-ns16550-uart driver started
/pci/pci-isa/generic-ide: sun:bus-generic-ide driver started
/pci/pci10b8,5@a,0: sun:pci-epic100-ether device started
/pci/pci10b8,5@a,0: Ethernet Address 00:e0:29:3c:6c:7f
IOM: SOFTINTR DISABLED (-31). Using an Interrupt thread
IOM Init cluster space from: 0x7bc1f000 to: 0x7bc3f800 [65 items of size: 2048]
IOM Init io-buf pool from: 0x7bc3f850 to: 0x7bc3fd70 [8 items of size: 164]
IOM Init raw io-buffer pool from: 0x7bc3fd70 to: 0x7bc411f0 [32 items of size: 164]
Copyright (c) 1992-1998 FreeBSD Inc.
Copyright (c) 1982, 1986, 1989, 1991, 1993
        The Regents of the University of California.  All rights reserved.

max disk buffer space = 0x10000
/rd: sun:ram--disk driver started
C_INIT: started
C_INIT: /image/sys_bank mounted on /dev/bd00
C_INIT: found /image/sys_bank/sysadm.ini
C_INIT: executing start-up file /image/sys_bank/sysadm.ini
bpf: ifeth0 attached
IOM: ifnet ifeth0 bound to device /pci/pci10b8,5@a,0
bpf: lo0 attached
C_INIT: Internet Address: 129.157.197.88
C_INIT: RARP Network Initialization OK
ifeth0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        inet 129.157.197.88 netmask 0xffff0000 broadcast 129.157.255.255
        ether 00:e0:29:3c:6c:7f 
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
        inet 127.0.0.1 netmask 0xff000000 
C_INIT: rshd started

Issue a command to the target system to make sure things are working properly. For example:

$ rsh target_hostname mount
root_device on / (pdevfs)
devfs on /dev (pdevfs)
devfs on /image (pdevfs)
/dev/bd00 on /image/sys_bank (msdos)