bootMonitor(1M)

NAME | DESCRIPTION | DIAGNOSTICS | ATTRIBUTES | SEE ALSO

NAME

bootMonitor- load and execute standalone programs over the network

DESCRIPTION

The bootMonitor utility uses standard network protocols over an Ethernet line to load and boot a ChorusOS system image. This system image must be an ELF binary.

The bootMonitor utility is embedded in a ChorusOS system image and can be put on a disk or into flash memory. The bootMonitor system image contains a light version of a ChorusOS microkernel, with all the drivers needed for ethernet network access and the embedded bootMonitor utility.

As soon as bootMonitor is loaded and starts running, it displays a status message similar to the following:

Boot Monitor Loader (v1.0)

This message shows the version number and system architecture for bootMonitor. The bootMonitor utility will then search for a boot configuration given in the BOOTCONF environment variable. If one is given, the corresponding boot agent is triggered (see bootAgent(1M)).

If no boot configuration is given, the default boot agent is triggered. The default boot agent is the CONS agent.

RARP Configuration File

The RARP boot agent works without a configuration file. However, using one is more flexible than directly loading a boot file. It implies a second TFTP load, to get the bootable system image, and also allows you to choose a boot server and the name of the boot file without requiring the intervention of system administrators.

The name of the file that the boot agent tries to load, using TFTP requests on the RARP server, is built from the target IP address in hexadecimal. For example, if the target IP address is 204.216.27.18 then the filename is CCD81B12.ChorusOS.5.0. If this file does not exist, then bootMonitor tries to load a file with the name, CCD81B12. The server location of this file depends on how the TFTP daemon started. The file can usually be found in the /tftpboot directory.

RARP Configuration Parameters

The following parameters are recognized by bootMonitor

BOOTSERVER=string

This is the Internet address of the remote system containing the boot file required. The Internet address should be in quad decimal dotted notation.

BOOTFILE=file name

This specifies the file name of the boot file required. If the remote TFTP daemon is running with a specified "base" directory, this name is referenced on the server relative to this directory. For example, BOOTFILE=chorus would correspond to /tftpboot/chorus on a server running UNIX with the tftpd base directory set to /tftpboot. If the TFTP daemon on the remote server is not running with a specified base directory, the file name must be fully specified and all directories leading to the file must be accessible to any user. For example, BOOTFILE=/home/kernels/chorus would correspond to /home/kernels/chorus on the server running UNIX. Both /home, and /home/kernels would need public read and execute permissions, and the file /home/kernels/chorus would need public read permission.

Each configuration parameter must begin on a new line. White space is ignored up to the first non-white space of the parameter value, after which all characters are taken as part of the value. A line containing a "#" in the first column is considered a comment.

DIAGNOSTICS

The following is a list of bootMonitor error messages and their meanings:

Not an elf image

The boot file is not a ChorusOS bootable system image.

No adapter found

There is no ethernet adapter on the target.

Can't initialize ethernet driver

The ethernet address of the ethernet adapter cannot be found or the ethernet device cannot be opened.

Badly formatted BOOTSERVER parameter

The BOOTSERVER parameter in the configuration file is not a valid IP address.

Badly formatted BOOTSERVER parameter

The BOOTSERVER parameter in the configuration file is missing.

Loading file chorus on server ...: Failed!

The file is not present on the server.

Check your RARP/BOOTP/TFTP configuration

The boot file cannot be found.

ATTRIBUTES

See attributes(5) for descriptions of the following attributes:

ATTRIBUTE TYPE	ATTRIBUTE VALUE
Interface Stability	Evolving

SEE ALSO

bootAgent(1M)

NAME | DESCRIPTION | DIAGNOSTICS | ATTRIBUTES | SEE ALSO