BOREALIS HITCHHIKER'S GUIDE
The master copies of the source code for Borealis utilities are in CVS under the borealis/utility/unix/, borealis/utility/windows/, and borealis/utility/cc/ directories. Users can install copies in local directories or they can be installed at each site. Installed copies of the Unix utilities at Brown are in:
/pro/borealis/utility/unix/
The borealis.dtd can be referenced from your xml file using:
http://www.cs.brown.edu/research/borealis/borealis.dtd
At Brown copies of the automake programs needed to build Borealis are in the /pro/borealis/software/common/bin/ directory.
At Brown the dependent packages are already built and installed. You can either use these copies directly or make your own local copies. If you need to work in a stable unchanging environment, make a local copy and then periodically update your local copy. This will ensure they do not get changed while doing critical work. The most recent packages are under the /pro/borealis/software/ directory. Copies built with different versions of gcc are in subdirectories such as /pro/borealis/software/gcc411/.
The Borealis CVS repository is at Brown. The CVSROOT for external users is ${USER}@ssh.cs.brown.edu:/pro/borealis/cvs. At Brown you can just use /pro/borealis/cvs.
If you need to work in a stable unchanging environment, work out of your sandbox and do not perform updates. Anytime you do perform an update you should always save your previous sandbox so that you can recover. The checkout.borealis.sh script will save your sandbox and then perform a checkout of either borealis or nmstl.
The borealis/test/valid/ directory has automated validation tests. These regression tests return pass or fail conditions.
The borealis/test/simple/ directory has tests that consist of a single source file and are run concurrently with the Borealis system.
The borealis/test/composite/ directory has tests that consist of several source files and are run concurrently with the Borealis system.
The borealis/test/unit/ directory has tests that consist of a single source file and are run as standalone tests. Each test exercises a Borealis component and does not require a complete Borealis build.
The borealis/test/developer/ directory has tests for developers. They are unsupported.
The game-demo branch is being used by Yanif's gaming group. Yanif plans on merging any bug fixes and new functionality into the main branch.
Brad is managing the Developer Links web site and keeps the master copy in a local directory. The visible pages at Brown are in:
/pro/web/web/research/borealis/developer/
They are copies so do not update them. Let Brad know if you want to make changes or he can make the changes for you.
They public Borealis web pages are managed collectively by the group. They are kept in:
/pro/web/web/research/borealis/
Small data files (under 1 MB) can be checked into the CVS (as binaries) under the borealis/data/ directory. Large data files are manually mirrored. Right now we don't have any large datasets available, but the /pro/borealis/data/ directory is where new large datasets should be added.
Some code has been used temporarily for experiments in Borealis and has been removed. Stale code that might have some future use is kept in subdirectories under the borealis/utility/stale/ directory.
The following machines are dedicated to the data management group. When you login to a cube, run the who command to see if anyone is using it. If so, check to see that you don't interfere with ongoing experiments. If you want to use them for a while, let other group members know. The fast machines are not for dedicated experiments and are free for general use.
Cubes:
128.148.37.37 borealis 128.148.37.56 yblue 128.148.37.58 ysilver 128.148.37.59 yblack 128.148.37.60 ygreen 128.148.37.48 xblack 128.148.37.49 xsilver 128.148.37.50 xyellow 128.148.37.52 xblue 128.148.37.54 xgreen