
This package includes a 3B2 executable for UCU.  I modified it
to enable hardware flow control on EPORTS boards that support
it.

Greg Gulik

[We now return you to the original README]
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 

                   This is UCU. Unlisys Call Up - Tool.
                            U(nix) call Unix.

       Ucu is written to run on Unix Sys V Rel 3 (and possibly 4) 
       machines as a replacement for the standard cu and other 
       PublicDomain/Freeware Software. 

       Ucu is a serial communicationsprogram that supports the 
       standard HoneyDanBerUUCP  environment. Ucu uses all the 
       Sysfile-features, enabling you to define your own 
          Systems, Dialers, Devices file(s) for usage with Ucu.


       Ucu was successfully tested on the following platforms:

		Sys V R2, m68k,  Force VME/010  (YEAH !)
		Sys V R3, m88k,  AT&T Sys Vr3.2 
		Sys V R3, i386,  Interactive Unix 2.*.* & 3.0
		Sys V R3, i386,  SCO UNIX/386 ...
		Sys III,  i386,  Xenix 386 3.2 ???
		Sys V R4, i386,  Dell UNIX Sys V Rel. 4 V.1
		Sys V R4, i386,  Interactive Sys V Rel. 4 V.3
		Posix,    i386,  Linux 0.99pl2 (gcc 2.3.3)
		Sys V R3, mips,  Irix 4.0.* 
		SunOS 4.1.1 (compiled with /usr/5bin/cc)

       Ucu is written for interactive use, taking the three best 
       parts from cu, kermit and pcomm enabling you to:

       - talk directly to the modem               (kermit/cu/pcomm)
       - use a builtin dialers-script             (cu)
       - use external file transfer-protocols     (pcomm)

       Other features of Ucu are

       - interpretation of dialing-errors (e.g. BUSY, NO CARRIER)
       - multiple dial-retries with different entries for the same 
         system or given number.
       - being 8bit clean.
       - being (hoply) fully compatible with standard cu and the
	 UNIX environment.


       See the section Files in the manpage,  read the INSTALL-file
       and look in the directory EXAMPLES for example files for the 
       different types of usage, or look it up in your uucp-management
       book.

       Note:
       All Ucu-files should belong to uucp as owner. if your Systems
       and/or Systems.ucu files contain passwords, they shouldn't be 
       readable for anyone but uucp. (400). Ucu has to be setuid uucp,
       if you want to restrict usage to special people do this by
       giving execution-permission just to a special group.

       
       Future-Plans:

       - Port to BSD environment.

       - Something we haven't thought of yet.
	

       Authors:

       Ucu was developed by
		Robert Rothe, Max Bluecher and the seven dwarfs 
		c/o Unlisys
		Hohenzollerndamm 7
		1000 Berlin 31
		Germany

	Email:
		Max Bluecher -> mbl@purple.in-berlin.de
			..!uunet!unido!fub!unlisys!purple!mbl
		Robert Rothe -> rot@unlisys.in-berlin.de
			..!uunet!unido!fub!unlisys!rot
		Seven Dwarfs -> ucu-bugs@unlisys.in-berlin.de
			..!uunet!unido!fub!unlisys!ucu-bugs

	Bugreports:
	Bugreports or Questions are welcome to the following
	Email-address:
		ucu-bugs@unlisys.in-berlin.de
		..!uunet!unido!fub!unlisys!ucu-bugs	

	Thanx:
		Thanx to all Ucu-Testers ! 
		Special Thanx to Uwe Doehring <gemini@geminix.in-berlin.de>
		for all his suggestions and fixes !


       Copyright:

       Ucu is Freeware but NOT Public-Domain ! The Authors have
       full copyright.

       Here are the conditions under which you may copy and distribute
       Ucu. The goal of these terms is to spread Ucu as widely as 
       possible while preventing others from making a profit with it
       or putting restrictions of any kind on it.

       1. You can freely copy Ucu, and you may give copies of Ucu to
          everyone.

       2. Ucu has to be distributed as the complete package posted
          to Usenet by its author.

       3. Vendors may bundle Ucu with their products as long as they
          a) tell their customers (somewhere in the written documentation)
             that UCU is freeware, wasn't developed by the vendor, and the
             vendor doesn't have the copyright for Ucu. 
          b) provide the complete original package in addition to their
             customized version. Customization means modification of
             the configuration files.
          c) tell their customers (somewhere in the written documentation)
             where the original package is located on the distribution
             media.  

       4. Changes to the sources are only allowed for private use.

       5. The authors aren't liable for any damage or loss of data caused
          directly or indirectly by or not by Ucu.


       Bugreports:
            Please mail Bugreports to ucu-bugs@unlisys.in-berlin.de
		(..!uunet!unido!fub!unlisys!ucu-bugs)

