<para>Julia Menapace first coined the term ``Deja Gnu'' to describe an
earlier testing framework at Cygnus Support she had written for
<command>GDB</command>. When we replaced it with the Expect-based
- framework, it was like DejaGnu all over again... But more importantly, it
+ framework, it was like DejaGnu all over again. More importantly, it
was also named after my daughter,<ulink
URL="mailto:deja@welcomehome.org">Deja Snow Savoye</ulink> (now 12
years old in Sept of 2002), who was a toddler during DejaGnu's
URL="http://nis-www.lanl.gov/~rosalia/mydocs/docbook-intro.html">free
GNU DocBook tools</ulink>) format.</para></listitem>
- <listitem><para>NT support. There is beta level support for NT
- that is still a work in progress. This requires the <ulink
- URL="http://sources.redhat.com">Cygwin</ulink> POSIX system
- for NT.</para></listitem>
+ <listitem><para>Windows support. There is beta level support for
+ Windows that is still a work in progress. This requires the
+ <ulink URL="http://www.cygwin.com/">Cygwin</ulink> POSIX
+ subsystem for Windows.</para></listitem>
</itemizedlist>
- <sect2 id=cygwin xreflabel="NT Support">
- <title>NT Support</title>
+ <sect2 id=cygwin xreflabel="Windows Support">
+ <title>Windows Support</title>
- <para>To use DejaGnu on NT, you need to first install the
- <ulink URL="http://sources.redhat.com/cygwin">Cygwin</ulink>
+ <para>To use DejaGnu on Windows, you need to first install the
+ <ulink URL="http://www.cygwin.com/">Cygwin</ulink>
release. This works as of the B20.1 release. Cygwin is a POSIX
- system for NT. This covers both utility programs, and a libray
- that adds POSIX system calls to NT. Among them is pseudo tty
- support for NT that emulates the POSIX pty standard. The
+ system for Windows. This covers both utility programs, and a libray
+ that adds POSIX system calls to Windows. Among them is pseudo tty
+ support for Windows that emulates the POSIX pty standard. The
latest Cygwin is always available from <ulink
- URL="http://sources.redhat.com/cygwin">this location</ulink>. This
+ URL="http://www.cygwin.com/">this location</ulink>. This
works well enough to run <emphasis>"make check"</emphasis> of
- the GNU development tree on NT after a native build. But the
- nature of pty's on NT is still evolving. Your mileage may
- vary...</para>
+ the GNU development tree on Windows after a native build. But the
+ nature of ptys on Windows is still evolving. Your mileage may
+ vary.</para>
</sect2>
<para>Follow these instructions as closely a possible in order get a good insight into how DejaGnu works, else you might run into a lot of subtle problems. You have been warned.</para>
<para>It should be no big problems installing DejaGnu using your package manager or from the source code. Under a Debian/GNU/Linux systems just type (as root) <programlisting>apt-get dejagnu</programlisting>. These examples were run on a primary machine with a AMD K6 and a Mac Powerbook G3 serving as a remote target.</para>
-<para> The tests for Windows were run under Windows NT using the actual cygwin version (1.3.x as of October 2001). It's target system was a PPC embedded system running vxWorks.
+<para> The tests for Windows were run under Windows NT using the actual Cygwin version (1.3.x as of October 2001). It's target system was a PPC embedded system running vxWorks.
</para>
<sect1>
<sect2>
<title>Windows</title>
-<para>On Windows systems DejaGnu is part of a port of a lot of Unix tools to the Windows OS, called cygwin. Cygwin may be downloaded and installed from a mirror of http://sources.redhat.com/cygwin/. All examples were also run on Windows NT. If nothing is said, you can assume that you should get the same output as on a Unix system.</para>
+<para>On Windows systems DejaGnu is part of a port of a lot of Unix tools to the Windows OS, called Cygwin. Cygwin may be downloaded and installed from a mirror of http://www.cygwin.com/. All examples were also run on Windows NT. If nothing is said, you can assume that you should get the same output as on a Unix system.</para>
-<para>You will need a telnet daemon if you want to use a WindowsNT box as a remote target. There seems to be a freeware telnet daemon at http://www.fictional.net/.</para>
+<para>You will need a telnet daemon if you want to use a Windows box as a remote target. There seems to be a freeware telnet daemon at http://www.fictional.net/.</para>
</sect2>
<sect2>
<title>Getting the source code for the calc example</title>
<para>If you are running a Debian distribution you can find the examples under /usr/share/doc/dejagnu/examples.
-These examples seem to be missing in RedHat's RPM.
+These examples seem to be missing in Red Hat's RPM.
In this case download the sources of DejaGnu and adjust the pathes to the DejaGnu examples accordingly.</para>
</sect2>
</sect1>
</sect2>
<sect2>
-<title>Using WindowsNT as host and vxWorks as target</title>
+<title>Using Windows as host and vxWorks as target</title>
<para>A more thorough walk-through will be written in a few weeks.</para>
<para>In order to test the vxWorks as a target I changed boards/standards.exp to reflect my settings (IP, username, password). Then I reconfigured vxWorks to include a FTP and telnet server (using the same username/password combination ad in boards/standard.exp).</para>
-<para>With this setup and some minor modification (e.g. replacing echo by printf) in my test cases I could test my vxWorks system. It sure does not seem to be a correct setup by DejaGnu standard. For instance, it still loading /usr/share/dejagnu/baseboards/unix.exp instead of vxWorks. In any case I found that (at least under WindowsNT) I did not find out how the command line would let me override settings in my personal config files.</para>
+<para>With this setup and some minor modification (e.g. replacing echo by printf) in my test cases I could test my vxWorks system. It sure does not seem to be a correct setup by DejaGnu standard. For instance, it still loading /usr/share/dejagnu/baseboards/unix.exp instead of vxWorks. In any case I found that (at least under Windows) I did not find out how the command line would let me override settings in my personal config files.</para>
</sect2>
</sect1>
<para>DejaGnu also supports running the tests on a remote
host. To set this up, the remote host needs an ftp server, and a
telnet server. Currently foreign operating systems used as
- remote hosts are VxWorks, VRTX, Dos/Win3.1, MacOS, and
- win95/win98/NT.</para>
+ remote hosts are VxWorks, VRTX, DOS/Windows 3.1, MacOS and Windows.</para>
- <para>The recommended source for a win95/win98/NT based ftp
+ <para>The recommended source for a Windows-based FTP
server is to get IIS (either IIS 1 or Personal Web Server) from
<ulink
URL="http://www.microsoft.com">http://www.microsoft.com</ulink>.
When you install it, make sure you install the FTP server - it's
not selected by default. Go into the IIS manager and change the
- FTP server so that it does not allow anonymous ftp. Set the home
+ FTP server so that it does not allow anonymous FTP. Set the home
directory to the root directory (i.e. c:\) of a suitable
- drive. Allow writing via ftp.</para>
+ drive. Allow writing via FTP.</para>
<para>It will create an account like IUSR_FOOBAR where foobar is
the name of your machine. Go into the user editor and give that
clear (i.e. not the same as your admin or personal
passwords). Also, add it to all the various permission groups.</para>
- <para>You'll also need a telnet server. For win95/win98/NT, go
+ <para>You'll also need a telnet server. For Windows, go
to the <ulink URL="http://ataman.com">Ataman</ulink> web site,
pick up the Ataman Remote Logon Services for Windows, and
install it. You can get started on the eval period anyway. Add
projects / platform / upstream / dejagnu.git / commitdiff