Information for CUCS Users
If you are within the Cornell CS department firewall and
want to set up
PREDATOR,
you should be reading this. This page tells you how to set up
a version of the system with source code. You will then need to
compile the source code to build a local copy of
PREDATOR.
Instructions for how to build the system are available through links
from the current public release page.
Just follow the instructions there, skipping the part that requires
you to download the code (since you are getting that locally).
Windows NT 4.0 Setup
Setup on Windows NT 4.0 is easy. Go to
\\bigbird.cs.cornell.edu\praveen\predator\nt_proj and
run (or double-click on) setup.cmd.
This may give you a bunch of warnings about failure to create
drives. Follow the instructions carefully, read the README
when prompted to do so, and setting up the system is a breeze.
The "master copy" of the system is maintained in a RCS repository
on a Unix file system. What you are actually doing during
setup is obtaining a copy of the system for your use.
There are two confusing issues, both related to mounting the
Unix file system with the RCS repository.
- Access to a Unix filesystem from NT is supported by the
Samba server. If you have NT Service Pack 3 installed,
there may be a problem using Samba. The adm home page
adm.cs.cornell.edu tells you how to fix this problem.
- When trying to mount the Unix filesystem from
sunup.cs.cornell.edu, you will be asked for the password
for sunup/praveen. Type in _YOUR_ Unix password (it wants
yours, not mine!).
Solaris Setup
The instructions in the public release tell you the various
steps to set up the system from the public release. You should follow
these steps, except for steps 2, 3, and 4 which ask you to download a tar
file and unzip it. Instead, do the following:
- Create the directory (typically called PREDATOR) in which you want
to set up the system.
- Make a soft link ("ln -s") to ~praveen/PREDATOR/xxx/RCS.
- Invoke "co RCS/*". This should put a Makefile into the directory.
- Make sure you have Gnu make as the default "make" in your path
(you can find out by typing "which make") and then invoke "make codeonly".
This should check out a copy of the code into a directory tree called
"code".
- Continue following the instructions for the public release. When
editing the environment variables in Step 6, make sure to also change
PREDATOR_LAIR to point to /home/praveen/PREDATOR.
Other Resources
As a developer of PREDATOR,
you can:
- Join the "predator" Unix group. This allows you to make changes to
the source code and check it back in. Contact Praveen if you should be
in the group.
- Join the "predator" mailing list. Again, send mail to Praveen. A lot
of exciting stuff gets posted here (and I'm selling a bridge you'll really
love to buy).
- Add yourself to the predator group web page (see the current group page). Contact Ivan Oprencak (ijo) for this.
Mail user support: predator-support@cs.cornell.edu
.... Back to PREDATOR Home Page