seperated node in the /os/nodes table.

Taken from the man page (ntip.1):
----
     Ntip differs from the traditional tip in a number of ways:

     1.   It does not support calling a remote system, all auto-dialing code
          has been removed.

     2.   All the cheezy file transfer support has been removed.

     3.   Most of the tilde escapes have been removed.  Mostly these were the
          file trasfer related ones.  See below for what remains.

     4.   Ntip ignores 90% of the remote(5) capabilities.  You can set the
          baud rate (br) and the device (dv).  Period.

     5.   All of tips variables are still present, but most don't do anything.
          It is left as an exercise to the interested user to differentiate.

     6.   By default, it operates in ``raw'' mode instead of the usual
          ``cbreak'' mode.  This means that all input processing (if any) is
          performed by the remote system.  Raw mode also disables
          ``raisechar'' and ``force'' variable interpretation.  Yes, you can
          actually run emacs on an ntip line (modulo the '~' thing).

     7.   Tip is the poster-child for fork-without-exec, creating separate
          reader and writer processes executing ``the same code.''  Ntip is a
          child of convenience and consists of a single process using
          select(2).

     8.   Ntip no longer uses uucp(1) style locking.  It relies on the TIOCEX-
          CL ioctl (see tty(4))  to provide ``reasonably mutually exclusive''
          access.  While it is still technically possible that two parties
          could open the same line and both get ``exclusive'' access to it, we
          consider this to be the source of amusing anecdotes rather than a
          bug.
----

direct_link scores that pop up.

files.  Note: none of the backend has been written yet.

Also did a number of minor bug fixes.  The most serious bug showed up when
you have a topology with no links.

code I found in /foo/x/mike/src/capture/capture.c. Second, add a -r
option to open up a second log file called the "run" file, which is
intended to be used for the experiment session log. This log is
restarted with a SIGUSR1. Third, add SIGUSR2 handler to close the
pty side of the capture, which has the nice side effect of causing tip
to exit gracefully.

checking.  Also made it so that .1 addresses were no longer assigned and
it now works when run on IR files that already have a /ip section.

some informative messages instead of just going away for 5 minutes.

STDOUT so the web page has something to show for itself.

rest to STDERR.

data in the database to be used when nfree runs.

option list, use a plain list instead. Simplify the DB queries now
that I'm a joining fool, and put in a proper confirmation step for
ending an experiment. Yippie.

on paper. tmcc runs on the testbed nodes. The linux and freebsd directories
have the scripts and skeleton passwd/group file stuff. There are makefiles
in those directories for installing on the testbed node (typically before
you cut an image!).

For use on testbed nodes in ~root/.ssh/authorized_keys . Should be mode
600.

error checking and now pulls defaults from the database.  Also fixed a
bug in set-dnard-os with ranges and set-node-os now takes a PERL regex as
a nodespec (actually translates to the regexp /^nodespec$/).

Note: handle_os currently has the delay node OS hardcoded to
FBSD40-STD.  This should eventually come from the database.

Also the error checking is not completely tested yet.  However, the
correct case works and handle_os.tcl had no error checking.