issue 0

runtest aborts unless you copy config.guess into ~/dejagnu.test

issue 1

instead of putting CALC=`pwd`/calc on the commandline, I had to put
 set CALC /path/to/calc
in ~/.dejagnu.

issue 2

paths of the example calc program.
You wrote
> 
> ng>:~/dejagnu.test$ cp /usr/share/doc/dejagnu/examples/calc/configure.in .
> ng>:~/dejagnu.test$ cp /usr/share/doc/dejagnu/examples/calc/Makefile.am .
> ng>:~/dejagnu.test$ cp /data/dejagnu/dejagnu.ng/calc.c .
> ng>:~/dejagnu.test$ cp -r /usr/doc/dejagnu/examples/calc/testsuite/ .
> 
but I had to do
wget ftp://ftp.gnu.org/pub/gnu/dejagnu/dejagnu-1.4.1.tar.gz
tar -xzvf dejagnu-1.4.1.tar.gz
 cp dejagnu-1.4.1/example/calc/{configure.in,Makefile.am,calc.c,testsuite} .
as redhat doesn't include calc in the dejagnu package,
and anyway calc.c and configure.in should come from the
same directory, no?

issue 3

the tutorial says

> 5.3 Remote testing "Hello world"
> 
> As a final step we will transform our above "hello
> world" example to the remote equivalent. This can be
> done by adding the following lines to our file remote_echo.exp.
> 
> test "Remote_send Hello World"

but the word 'set' is missing.  It should read

set test "Remote_send Hello World"

issue 4

The tutorial should make it more clear that unless you do
export DEJAGNU=~/site.exp
dejagnu will ignore the ~/boards directory!!

issue 5

The tutorial should probably explain that the
set_board_info shell_prompt "remote"
line is very important; the argument must be
a unique word that shows up only in the shell
prompt, not in the telnet welcome message.  Failure to
heed this causes silent errors when doing remote stuff.

I like using myusername@thehostname, as Red Hat uses
that scheme for its prompts, and it can't be confused with
the telnet welcome message.