This distribution has been tested on the following operating systems,
using gcc version 2.6.0 or above:

	Solaris 2.5

It has been ported to, but not thoroughly tested, on:

	Linux 2.0.27, Debian flavor
	Digital Unix 3.2C

It has been tested on a MicroAnnex XL running version 10.0 of the
server software. It shouldn't be too hard to get it working on
others...  There are some hardcoded strings to deal with
authentication in console.c:server_auth_handler(), and I tried to make
the telnet protocol stuff in console.c:auth_iac_handler() easy to
amend.

There is lots of logging, especially when debugging is enabled.

It should build on the above systems without any trouble. If you want
it to run on something else, pick the config file of the most similar
machine (in config/), make a new copy for your system type, and check
the definitions.

You may want to edit the configure script to have it recognize your
new system. Some day I'll switch to using a real configure script. In
the meantime, the possible DEPDEFs that the code knows about are:

   USE_PROTOS

      Use function prototypes, recommended.

   POSIX

      Use things which are supposed to be POSIX standard. Solaris and
      Digital Unix should have this defined.

   SOLARIS, OSF, LINUX, SUNOS

      Define the operating system. This is useful mostly for including
      header files that are different across systems, and for dealing
      with system-specific quirks.

   DEBUG

      Include debugging code, especially asserts. Setting to higher
      values makes for more debugging output.

   NEED_VSNPRINTF, NEED_SNPRINTF, PIPELOOP

      If your system doesn't have vsnprintf() or snprintf(), you'll
      need to define these to compile in the supplied versions defined
      in pipeloop.c.

   I_UNISTD_H, I_TIME_H, I_SYS_SOCKIO_H

      These are used to include the header files unistd.h, time.h, and
      sys/sockio.h. Although we could use the operating system to determine
      which of these should be included, I kept these separate because
      there is usually more conformity in their usage. The operating
      system definitions should be used more sparingly.

Make definitions of interest to the config files are:

   CC, COPT, CDEBUG

      Compiler, optimization, and debugging flags.

   DEPDEF

      Definitions that apply to this system type, like -DPOSIX (see above).

   DEPOBJS

      Other object files that need to be linked in, like pipeloop.o,
      that other systems may not need.

   DEPLDFLAGS

      Special flags to load with, like -lsocket. This def is put at
      the end of the loading command.

   MAKE

      Maybe your make won't work. You could define this to be gmake
      or something.

   RANLIB

      If you need to run ranlib on libraries, set this to the program
      and arguments you need. Usually "RANLIB = ranlib" will work.

If you succeed in porting it to a new system, please send me a context
diff so that I can include it in later distributions. You can reach me
by going to http://www.site17.org/.
