The following table describes the directory conventions used in this book.
Table P-1 Directory Conventions
Directory |
Description |
---|---|
download_dir |
Directory containing the ChorusOS 5.0 download files. Example: /home/user/downloads/ChorusOS_5.0/ |
extract_dir |
Directory containing sufficient space to extract the delivery. This directory can be a local or an NFS mounted disk that has "write" permission. Example: /home/user/extract/ |
install_dir |
Directory where you install the ChorusOS product. Example (also default): /opt/SUNWconn/SEW/5.0-processor_family where processor_family is one of the following: UltraSPARC, x86, PowerPC, MPC8xx Note that, during installation, you can choose the installation directory other than /opt/SUNWconn/SEW/. However, the 5.0-processor_family directory containing the ChorusOS directories and files is automatically created in the directory you specify. |
build_dir |
Directory where you configure and build the system image. This directory can be a local or an NFS mounted disk, but you must have "write" permission. Example: /home/user/chorusos/build/ |
root_dir |
Directory containing the ChorusOS file system. Example: /install_dir/chorus-family/os/root |
mount_dir |
Directory on the host containing a file system you want to mount on a target. Example: host:/install_dir/chorus-family/os/root |
source_dir |
Directory containing the source files. Example: install_dir/chorus-family/src/ |
family is one of the following:
usparc for UltraSPARC IIi/III
x86 for Intel x86/Pentium
ppc60x for the Motorola PowerPC 60x and 750 processor family and the PowerQUICC II (mpc8260) microcontroller
mpc860 for the Motorola PowerQUICC I (mpc8xx) microcontroller.