old-history-2

一个通讯程序源码

14. Some work (largely in the dark) has been done to handle
differences between ISC and SCO tty naming.  The new manual entry says
of the -l startup switch:

  The argument to the switch is the base name of the tty (e.g., "tty1a" or
  "acu0").  On SCO, since ttys are all named consistently according to the
  "/dev/ttyxx" form, you may omit the "tty" (e.g., "1a" or "4g").

The new manual entry says of the tty name fierld in the dialing directory:

  A specific line is specified by using the base name of the tty (e.g.,
  "tty1a" or "acu0").  On SCO, since ttys are all named consistently
  according to the "/dev/ttyxx" form, you may omit the "tty" (e.g., "1a"
  or "4g").

This means than on ISC you must now fully specify the base name
of the tty.  On SCO, you now have the -option- of doing the same or
you may continue to use the two character suffix.

I believe that now:

  on SCO, you may use any tty name whose base name begins with "tty".
  on ISC, add tty names whose base name begins with "acu"

15. Miscellaneous other (nonvisible or debugging) changes were made.

:EDITS: summary:
----------------
Configure                   change FASI_IN_USE to FASI
ecu.c                       add memstat 
ecu.c                       jpm@logixwi fix: HZ getenv test wrong sense 
ecu.c                       soup up -l for ISC vs. SCO 
ecu.h                       configurable lock directory 
ecuLCK.c                    SCO_TTY_NAMING considerations 
ecuLCK.c                    configurable lock directory 
ecuLCK.c                    race with ecuungetty over lock resolved 
ecucmd.h                    add memstat 
ecuicmd.c                   add memstat 
ecuicmd.c                   turn off memstat after frustrating evening 
ecuicmhelp.c                when editing string, set cursor to end 
ecuicmhist.c                new ttygets botched command history handler 
eculine.c                   SCO_TTY_NAMING considerations 
eculine.c                   baud rates below 300 get two stop bits 
eculine.c                   remove unused externs 
eculock.c                   US_WEGOTIT handling 
eculock.c                   configurable lock directory 
ecuphone.c                  soup up tty name for ISC vs. SCO 
ecuphone.c                  w subcommand was not asking both questions 
ecuphone.c                  when editing string, set cursor to end 
ecusetup.c                  ISC tty names 
ecuungetty/ecuungetty.c     US_WEGOIT handling 
ecuungetty/ecuungetty.c     add debug log event code 
ecuwinutil.c                when editing string, set cursor to end 
expresp.c                   \n sent CR not NL 
expresp.c                   detect NULL expect string 
expresp.c                   nap min of hzmsec if \m 
hdbintf.c                   US_WEGOTIT handling 
kbdtest3.c                  add parity reporting 
kbdtest3.c                  some terminals reinvent parity bit's use 
lint_args.h                 afterlint-creation 
logevent.c                  use static logname 
makedirs.c                  need smart_fork for XENIX 
mkdirs.c                    how did compile succeed without signal.h? 
mkdirs.c                    no need for sys/wait.h + XENIX doesn't have it 
models/nonansikeys          add new Metro Link server entry
nonansikey.c                allow any code as first in key sequence 
nonansikey.c                look for nonansikeys in ECULIBDIR too 
pcmd.c                      add nap -1 return and proctrace 
pcmd.c                      nap -m test wrong sense ... old bug! 
utmpstat.c                  US_WEGOTIT handling 
utmpstatus.h                add US_WEGOTIT 
z/Make.src                  neat used wrong rm args
zgcc                        thanks for the -p1 suggestion to [e-mail]

README.P2           ECU 3.10 Patch 2        Tue Aug 13 16:29:11 EDT 1991

This describes patch 2 to ECU 3.10, bringing the program to
version 3.12. 

The majority of this patch deals with the way SCO and ISC misimplement
the nap() system call.  A lingering problem with the interactive
command history handler is also fixed (pressing erroneous function keys
caused the display to become garbaged).

ISC and SCO UNIX nap() misbehave.  This kludge doesn't return the
proper value (the actual time slept), but at least it does not make
a mockery of the manual page.  It says:

     NAP(S)		       UNIX System V			NAP(S)

     Name
	  nap -	suspends execution for a short interval

     Syntax
	  long nap(period)
	  long period;

     Description
	  The current process is suspended from	execution for at least
	  the number of	milliseconds specified by period, or until a
	  signal is received.

     Return Value
	  On successful	completion, a long integer indicating the
	  number of milliseconds actually slept	is returned. If	the
	  process received a signal while napping, the return value
	  will be -1, and errno	will be	set to EINTR.

     See Also
	  sleep(S)

     Notes
	  This function	is driven by the system	clock, which in	most
	  cases	has a granularity of tens of milliseconds.  This
	  function must	be linked with the linker option -lx.

It appears nap() under UNIX 3.2.x has departed virtually entirely from
the manual page.  I'm beginning to look rather silly in several
milleus since I keep telling people SCO UNIX is a viable upgrade from
XENIX.  But process control people need some kind of timing capability
less than one second and we can't do it with nap or select.

nap(msec) is supposed to nap *at least* msec milliseconds.  However,
if msec is specified less than 1000/HZ + 1, it will not nap at all.
This was true for 3.2.0 and 3.2.1.

It is supposed to return the number of milliseconds it actually
slept.  Instead, it appears to "save up" the values and return them in
lots of 1000. This behavior is true for 3.2.2.

As it is nap() is nearly useless.  I believe select() suffers
from the same deficiency (< 1000 msec timeout becomes 1000 msec) but
I haven't "proven" it yet.

README.P3           ECU 3.10 Patch 3        Tue Aug 27 03:36:04 EDT 1991

This describes patch 3 to ECU 3.10, bringing the program to
version 3.13. 

Overview
--------

The patch fixes some problems with the previous release, adds new
functionality and adds support for SunOS 4.1 and ISC System V
Release 4.  I have tested it fairly well on a Sparc 1+ under
X11R4 (MIT Sun server and xterm at PL18) and SunOS 4.1.  I did my
best to integrate patches supplied by Lothar Hirschbiegel
(aega!lh).  Lothar has ISC SVR4 and his changes worked for him,
but I had to hack them since his patches were against the
"official" 3.12 and I applied them to sources already half-ported
to the Sun.  I hope they go well, but write if they don't.  I want
to hear of any success you might have with other SVR4 systems, too.

System V Release 4
------------------

> I cannot offer much information on this, since Lothar sent little more than
> patches and I have no access to a system for testing. 
> This is what I have:
> I've just finished porting ecu3.12 to SVR4. I have added my changes
> as a diff file, maybe this is of interest for you.
> The following points were added/changed:
> 
> 1. I have included a configuration option for SVR4 in config.c
> 2. ecu works fine with "ttymon" under SVR4. This means you don't need
>    FAS or something like this - bidirectional access to the serial ports
>    with the stock asy drivers is ok.
> 3. Because of some strange(?) behaviour in SVR4 curses I had to use
>    some terrible kludges to make it work clean. It's working as it is,
>    but there is obvilously room for improvement...
> 4. SVR4 has the same set of hardware handshake ioctl's as SCO does.
>    It's named differently (RTSXOFF and CTSXON), but it seems to work exactly
>    the same way. I have enabled the "RTS" option for SVR4 - hopefully this
>    is a standard feature (termiox) in *all* SVR4 versions, not just in
>    my ISC release... :-)
> 5. I'm still working on ecusz/ecurz. Outgoing transfer is doing fine, but
>    incoming transfer locks up the connection sometimes.
>    As soon as I have finished this, I could send you the cdiffs too.

SunOS
-----

I brought this up in relatively short order.  I may have gotten
what I paid for :-), but it seems stable.  The System V support
under SunOS was pleasingly similar to the SVR3 environment ECU came
from.  This release works on my Sparc 1+ with SunOS 4.1.1 and X11R4.
Some xterm VT100.Translations overrides are necessary to enable use of
certain keys unrecognized by the default xterm configuration.
Details are provided in the updated models/nonansikeys.  If the
recommended changes, you can do what I did to figure out how to
get this guy going:

  1. run xev and press the various function keys to see the
names you need to specify in the xterm translations.  
  2. edit the translations in nonansikeys example and put them in
your .Xdefaults file
  3. run kbdtest3 to get a kbdtest3.out file
  4. put this file's output into your ~/.ecu/nonansikeys file
(near the top, ahead of other xterm defs so it will be found first).
  5. try it
  6. when it works, send me the kbdtest3.out file along with the
VT100.Translations overrides you casme up with and a description of
the X environment you used.

There is also a new entry named 'sun' in models/nonansikeys for the
console.

Note on 'nonansikeys'
---------------------

This file was named when support was added to the original
SCO-only version to support keyboard/screens other than the
native multiscreen console.  Since the TERM name for multiscreens
is "ansi", it seemed reasonable to name the file nonansikeys.  It
now should probably be called 'nonSCOmultiscreenskeys', but that
name is too long for System V :-).  Before too many more
revisions, even SCO multiscreen key definitions will be read from
nonansikeys and maybe then will be a good time to rename the
file.  Anyway, this file and a good termcap definition takes you
a long way to supporting ecu on a wide variety of System V{,-ish}
platforms.

Fixes
-----

1.  The ANSI SD (scroll down) sequence was broken for consoles
other than SCO multiscreens.  It scrolled down n * COLS lines
instead of n lines.

2.  Editing the null phone directory entry (pressing 'e' in an
empty directory, editing and exiting) caused a core dump.  Now
you are prevented from editing a non-existent entry.

3.  Procedure commands with switch arguments longer than 8
characters caused stack corruption (unpredictable behavior
including core dump).  There is no call for switches this long,
but if present, the program should not explode.  Now, switches
longer thasn 8 characters (including the hyphen) are silently
truncated.  Should commands ever be added which could conceivably
evoke switch arguments that might approach the limit, either the
limit will be extended or error reporting will be added, or both,
as appropriate.

4.  # comments to the right of nonansikey key definition lines
erroneously included the # in the definition.  This may not have
been a bug in 3.12.  I may have added it during 3.13 development,
but it is gone now in any case.

5.  Previously, if the console line baud rate was not at least 4
times the tty line rate (roughly), the "no curses" mode was
forced during file transfer and could not be overridden.  Since
various video driver implimentations express verious pseudo-"baud
rate" settings, this was more often a problem than a feature.  If
the change causes you trouble, write me (or trying using Home pc
sz -N in lieu of Home pc sz, etc.).

6.  Previously, an effort was made to editorialize on your choice
of a tty device name.  This is no longer done.  On SCO, you
should use the lower case (direct) names, like tty1a, to get the
expected lock file names, but trying to second guess all the
vendor and third-party names was an unnecessary and
counter-productive stumpling block.  If you want to go for
/dev/swap, go ahead (I don't expect the ioctls to work -- or your
system :-> ).

7.  Andrew A. Chernov ([e-mail]) said:

1) HDB dialers may return connect speed as return code (!= 0)
 [ and the CONNECT string built by hdbintf.c prints this code -- wht]
 [his patch used - wht]
2) Using HDB Dialcodes file for phone numbers translation now
   (\D,\T escape sequence)