^{Highley Recommended, Inc.}

Portable Field Integration Test System Setup

The tadpole unit barnacle, has post operating system customizations so
the system will function as a portable development platform that can be
taken to other companies to work out integration issues with their
equipment.

Once the operating system has been install, currently Solaris 2.5.1, we
need to copy over to the tadpole system the directory tree:
    /pkg/sun/ife

It can be located anywhere, but needs to remain in the structure that
it is.  It consists of a customization script with template files to be
installed on the tadpole system.  The basic philosophy of the
customization is to create links for a parallel set of directories to
store local copies of the cross compilers and application source code.
The links are invisible when the node is in the company network as the
normal NFS mounts mask over them.

When the system is taken out of the network the user is prompted at
boot time as to whether they are connected to a "Production|LabUnit"
embedded box.  There are two init.d files that modify the hostname,
network address, xdm login screen, and XXXXXX.  These changes set the
system up to NFS serve the embedded product and allow the cross
compiler licensing to be portable.

To customize the system, change directories to where you copied the
customization tree and do:
    ./customize -help
You will get a print out of the steps in function order.  Note: before
you can copy over the embedded cross compilers you will need to mount
the configuration management root directory "/ccofc" and set a view.
However you should not NFS mount any file systems until you have
executed the "mkdirs" function which will create links that get masked
over by the NFS mounts.

The users are added by doing a "ypmatch developers aliases".  We use this
list to extract from NIS the user password entries which we use to
modify the local password and shadow files and to create a local home
directory.

Once the system is set up the users need to copy over the environment
files they need.  Then they need to logon to the tadpole unit, set a
view and execute the script "local_copy" located in the user local bin
directory.  This script will copy over the embedded box application
software to the tadpole system.  The system is now ready to take out of
the network and should be able function standalone.  For further
information about this system you can read the user instructions.

User Instructions

The tadpole system, barnacle, has been configured with the necessary
modifications to run as an independent development and integration
platform that will work with all versions of the embedded box and all
types of builds.  This system was tested with version 8 and version 10
of the embedded product with builds using Oasys compilers doing product
builds or hyperlink builds and using the Microtech compilers.

Home directories for all user listed as members of the e-mail list
"developers".  Users will need to logon the system and copy their user
environment files to the portable system by doing:
    - logon: barnacle
    - cp ~/.profile /export/home/"user"/. ; will copy the file .profile
	file from the users home directory to their home directory on
	the portable unit.
    - Repeat step above for each file or add a "-R" flag if your copying
        a directory and all files below it.

To put a copy of the application source code onto the tadpole unit:
    - logon: barnacle
    - clearcase setview ; view with rules set to select version needed.
    - local_copy ; execute script to copy source code to tadpole unit.

Having done the steps above your now ready to take the tadpole unit out
of the network by:
    - Logging off the system.
    - logon: off ; special account that shutsdown the system.
    - passwd: take2down

To connect the tadpole system to the embedded box use the null network
cable, marked with red tape, that is in the tadpole carrying case.
Connect the embedded box console serial port to the tadpole serial port
"A" with cable in the carrying case.

Power on the tadpole unit and you will be prompted to answer which kind
of embedded box your connected to, "Production|LabUnit".  The system
will then configure its self to serve the embedded box.

Build the software as you normally would, clearmake is not available,
use the make command.  Copy the build as you would normally to the
mount point, there is only one embedded box mount point as all mounts
are linked to one location.  Turn the embedded system on and "tip
box_console" in an xterm window.  You should be able to see the
embedded box booting up.