readme

一个通讯程序源码

.--------------------------------------------------------.
| ECU README - last revised Sat Sep 12 18:28:06 EDT 1992|
`--------------------------------------------------------'

This is ecu revision 3.20.  ECU is a asynchronous communications
program for these environments:

  SCO XENIX System V/286          ECU may be too large for '286
  SCO XENIX System V/386          ECU is stable on SCO XENIX/386
  SCO UNIX System V/386           ECU is very robust on SCO UNIX
  SCO ODT 1.x,2.0                 ODT is the same as UNIX for ECU

  ISC 386/ix 2.2 or later         Ports to these systems are
  ISC System V Release 4          not supported as regularly
  ESIX System V Release 4         and I cannot vouch for
  SunOS 4.1.[12]                  them at time of release 
                                  PLEASE GIVE ME FEEDBACK!

ECU (Extended Call Utility) is a research and engineering
communications program originally written for users of SCO UNIX
V.3.2/386 and XENIX V on 80286 and 80386 systems.  Support for
other systems has been added and further porting is possible with
"minor" effort to other systems based on or similar to UNIX
System V.

ECU provides the classic terminal communications facility of
passing keyboard data to a serial line and incoming data to the
computer video display.  In addition, a dialing directory, a
function key mapping feature, session logging, and other
basic features are available.  

ECU presents to the host a flexible "ANSI" terminal type,
accepting any valid video control sequences from MS-DOS or SCO
documentation as of late 1990.  It also fares well, though
imperfectly, with Sun and VT-100 in-band video control sequences.
Standards are great: everybody should have one, especially if
they call it "ANSI". For more information, refer to the manual
section titled "ANSI Filter."

Support for arbitrary video consoles is included.  I use ECU
(almost exclusively now) with an X11R4 xterm.  This release has
been tested extensively with xterms (particularly Metro Link
X11R5, SCO ODT 2.0 X11R4, SunOS 4.1 MIT standard distribution,
OpenWindows 2.0, and Roell's X386 1.1b).  Your terminal must be
fairly "smart", with insert/delete-line features,
erase-to-end-of-line, etc..  See "Supported Terminals" in the
manual.  Also check the note below named "KBDTEST3".

ECU supports numerous file transfer protocols: as of this
writing, XMODEM, XMODEM/CRC, XMODEM-1K, YMODEM/CRC Batch,
ZMODEM/CRC-16, ZMODEM/CRC-32, C-Kermit 5 and SEAlink are
supported.  For more information, refer to the manual sections
describing the individual interactive and procedure file transfer
commands.

A very flexible procedure (script) language is also incorporated
to automate many communications tasks.  In addition to augmenting
interactive tasks, by using shell scripts and ECU procedures, ECU
can perform batch-style communications sessions in an entirely
"unattended" fashion.

For applications too unwieldy for the procedure language,
"ecufriend" programs are supported.  Friends are spawned by ECU
having access to the shared memory segment containing an
ECU-managed "screen image" and other data and having use of the
attached communications line.

Gcc is supported for all programs in the release.  See the
configuration section and the note on gcc for important caveats.

Ports to ISC 2.2, ISC SVR4 and ESIX SVR4 and SunOS 4.1.1 are
fairly stable and useful, though not all features are working.
Also, the documentation suffers in covering these ports.

The doc subdirectory has all of the .txt files used to produce
ecu.man, the manual of sorts for the program.  A copy of it is
reluctantly included (net.bandwidth) for those who do not have
nroff.  I finally blew up my nroff with something related to
document length, so there are two documents, ecu.man and
proc.man.

*Please* take the time to read the (tedious) manuals and READMEs
even if you are a pre-3.20 user.  This will do me honor and
yourself justice because there are a lot of goodies in here,
many of which are not traditional features you'll be looking for.

--------------------------------------------------------------------

ACKNOWLEDGMENTS

MANY THANKS to those who helped me improve the program,
especially upaya!tbetz, [e-mail], [e-mail],
[e-mail], [e-mail], dug@kd4nc,
jts@ki4xo, jsm@n4vu, [e-mail], cma@tridom,
tabbs!aris, redi!donovan, neal@clkwrka, [e-mail],
mjb@mjbtn, tmcsys.uucp!lothar, [e-mail]
elastic!fche, genrad!rob and [e-mail].  There were
lots of others and I know I've forgotten someone who helped a
great deal; I apologize.

Very special thanks go to Dion L. Johnson at SCO for his untiring
and generous support.  Also, many kudos the guys at Metro Link for
their excellent X11R4/X11R5 package.  Yes, xecu has been born and is in
the works at last.  Right now, it is a telnet socket user only,
but serial I/O is on the way.  ECU may learn about telnet too.

Lothar Hirschbiegel <aega84!lh> did the ISC SVR4 port -- 
THANKS, Lothar!

Joseph H Buehler <[e-mail]> extended the SVR4
port to ESIX -- THANKS, Joesph!

Robert Lewis <[e-mail]> and John Dashner <wa4cyb!jmd>
proofread the manual.  This is tedious work and special thanks
go to them.

The 3.20 alpha team of 

    Clayton Haapala       [e-mail]            
    Cliff Yamamoto        [e-mail] 
    Jeff Liebermann       [e-mail] 
    John Dashner          wa4cyb!jmd                   
    Joseph H Buehler      sarto!jhpb                   
    Lothar Hirschbiegel   aega84!lh                    
    MarK J. Bailey        [e-mail]       
    Mark Ashton           n4hgf!ifsbd!cma              
    Robert Laughlin       [e-mail]                 
    Robert Lewis          [e-mail]             
    Robert Lipe           [e-mail]            
    Tim Sailer            [e-mail]                

worked diligently daily over many weeks.  If there are fewer bugs
in this initial release than in previous releases, you have them
to thank.  It would have been many more months before 3.20 saw
the light of day (if ever) without their support.

--------------------------------------------------------------------

HOW NOT TO START DOWN THE WRONG PATH HERE

C Kermit 5 is a much, much better product than ECU.  It runs
in zillions of environments, is much more robust and has many
better features.  I wrote ECU when there was nothing like it
available.  Since then, C Kermit has grown sliding windows
and an excellent script language.  C Kermit won't do X/Y/ZMODEM
(although you can get there from here).  It doesn't have a gnarly
shared memory interface for "friend" programs (I do not know
of any one but me who has used it).  C-Kermit has
hundreds of implimenters/testers, thousands of users and two
most righteous Captains (Frank daCruz and Christine Gianone)
behind it.  ECU has less than 10 developers and about 15 users :-).

I will happily maintain and improve ECU for those who want it,
but if you are not a C hacker and unabashed techie (or even if you
*are*), C Kermit 5 is probably the asynchronous package for you!

--------------------------------------------------------------------

MAKING AND INSTALLING

1.   Unshar all of the shars

     I do not put anything in shell archives that is intentionally
     dangerous, but it is very, very unwise to unshar as root.
     Unpack shell archives as an unprivileged user.

     Make a directory and cd into it.  Use an unshar program
     to extract all of the forty-odd parts of ECU and the three
     or so parts of the manual.  If you do not have unshar, it
     may be quicker to find one than to extract ecu without it.
     However, if you must, edit each shar and remove all lines
     prior to #!/bin/sh and then feed each file to /bin/sh, like

        /bin/sh < part

2.   Type ./Configure

     This procedure builds Makefiles for ECU specific to your
     system.

     You must have your native compiler available for this.
     If it unavailable and you have gcc, you can TRY:
       gcc -fwritable-strings -fpcc-struct-return -o config config.c
       ./config
     If you are running *SCO UNIX*, add -DM_UNIX to the above gcc line.
     This alternate procedure is not guaranteed to work with future
     patchlevels and releases (There will always be a way to do it,
     but I very likely will be counting on SCO MSC M_... predefines more
     and more).

3.   Configure will compile and run config. 

     Answer the questions.  If you are using a supported system,
     answering the few simple questions is all that is necessary
     to produce a usable configuration.  (If you are trying to
     port it, make your best guess, hack the Makefiles and sources
     and send them to me with your patches.)

     You will be asked the system type.  Respond according to
     the following table:

        System                         |   Type
     ----------------------------------+------------
       SCO UNIX (any version)          |     s
       SCO ODT (any version)           |
       SCO XENIX (2.0.6 or later)      |
     ----------------------------------+------------
       ISC 386/ix (2.2 or later)       |     i
     ----------------------------------+------------
       SunOS (4.1.1 or later)          |     S
     ----------------------------------+------------
       ISC SVR4                        |     I
     ----------------------------------+------------
       ESIX SVR4                       |     E


     If you answer SCO, you are asked which variety: XENIX/286,
     XENIX/386 or UNIX/386 prior to 3.2v4, or UNIX/386 3.2v4.

     Provided you did not opt for XENIX/286, you will be asked if
     you want to use the native cc or gcc.

     If you ask for gcc, you'll be asked if you have gcc 1.40 or
     not.  An obscure minor bug in 1.39 was fixed in 1.40 and
     it amounts to little effect as of this writing.  Answering
     no is safe, but future patches make make better use of the
     configuration information.

     You will be asked for a default tty line, baud rate and parity.
     The default for the default tty is  system dependent.  The
     defaults for baud rate and parity is 9600 and none.  You may
     override these with your personal preferences.

     You will be asked for the directory to install ECU and friends.
     library.  The default is /usr/local/bin.  If the directory
     does not exist, the install procedure will attempt to make it.

     You will be asked for the directory to use for a private ecu
     library.  The default is /usr/local/lib/ecu.  If the directory
     does not exist, the install procedure will attempt to make it.

     The config program will thank you (;->) and then build Makefiles
     from the Make.src files in each appropriate subdirectory.

     If you are porting to a new system, you will want
     to examine and modify the Makefiles before proceeding.

5.   The configure script suggests you "make depend".  This is
     unnecessary if you are building ECU for the first time.  Also,
     most patches will require you to rerun Configure.  Each time you
     reconfigure the software, it is automatically completely remade
     when you next run make.  Only if you anticipate making changes to
     the software is "make depend" necessary to ensure the code is
     properly made.

6.   Type 'make'.  Wait and watch a while.  This is a good time to
     be reading over doc/ecu.man and various READMEs.
     There are a great number of new features.  There are
     few incompatibilities ("I hate 'em").  The file HISTORY
     has some note on every change made since 3.16.  Unfortunately,
     HISTORY also contains technical/historical information of no 
     interest.

7.   Su to root, if not already there, and type 'make install'.

8.   The default models/funckeymap is copied to the ECU library
     as part of installing the program.  You will probably need
     to study and modify this file if you plan to use a console
     (user tty) other than the native console of your system.

9.   You must, as root, chmod +rwx your uucp locks directory.  In
     addition, if you are on a machine which ecuungetty does not