Ultrix -> Xenix/386 uucp problem

[William E. Davidsen Jr]

In article <192 at conexch.UUCP> root at conexch.UUCP (Larry Dighera) writes:
| [... my BSD to Xenix/386 problem ...]
| As I recall, Xenix' stty sane defaults to 8 bit no parity.  This causes the 
| Ultrix machine to get a garbled password.  Try adding CS7 PARENB to the 
| inital and secondary flags in /etc/gettydefs.  It worked for me.

  I am willing to believe that there is a parity problem, however I am
still looking for a useful solution. If I set default parity to even
everything else will go to hell. I can't afford to tie up one more line
just to let calls come in from one system.

  My alternative solution was to have the login call up a program other
than uucico which would reset the line parity and exec uucico. This
doesn't work, reason unknown. The line reset works, if I fork something
other than uucico it runs even parity. If I fork uucico I get no parity
again.

  To test this I put a sleep between the line set and the exec, then
looked at the line with stty from another terminal. The line was reset
to no parity when uucico started. I then manually used stty to force a
console even, and started uucico. When it timed out the parity was off
again (it may be resetting to sane).

  I even tried doing a fork, waiting for uucico to start, *then* setting
the line the even. Again it got reset to no parity. I have had three or
four people tell me that the parity may be reset in the BSD char script.
The sysmgr is willing (eager) to do this, but can't find any
documentation on how. Was this deleted from Ultrix?

  Still looking for any suggestion, and very happy at the support so
far. Hopefully I've stated the problem in more detail this time.
-- 
	bill davidsen		(wedu at ge-crd.arpa)
  {uunet | philabs | seismo}!steinmetz!crdos1!davidsen
"Stupidity, like virtue, is its own reward" -me