- *
- This work was supported by DARPA Contract
N66001-96-C-852
- 1
- Note that
all executable programs in the PLAN distribution are stored in the bin
directory in the PLAN directory-tree. These examples assume that you are
typing the commands from the plan directory.
- 2
- The actual names of the interface files
are not important, we just chose these for convenience.
- 3
- pland will look for the file EXP_IP_ADDRS in the current directory.
If you want to run pland from a different directory, you will have to
specify to pland where to find this file by using the -hf
option. This file must be present and must at least contain your
machine's IP address mapping.
- 4
- This is why
the argument given to pland's -ip option must match the port
portion of some network address in the interface spec file -- otherwise,
calls to thisHost() from inject will not have the proper network
address.
- 5
- In particular, the
evaluation is set to your machine's name, as returned by the Unix call gethostname, concatenated with the given inject port
- 6
- We'll see later that the resource bound is
irrelevant for this program!
- 7
- Earlier versions of PLAN required
that you use Ctrl-D rather than a semicolon. This was due to a poor
parsing definition. We allow the use of Ctrl-D rather than a semicolon for
backward compatibility
- 8
- There is
actually a third primitive, RetransOnRemote, but it is not described
here.
- 9
- Notice those funny
|'s around the function call name? These are syntax for defining
a value of type a chunk. More will be said about
chunks a little later.
- 10
- Note
that these are independent of the packet header