Xref: utzoo comp.unix.microport:369 comp.unix.xenix:1823 comp.unix.questions:6359 comp.unix.wizards:7504
Path: utzoo!mnetor!uunet!steinmetz!davidsen
From: davidsen@steinmetz.steinmetz.ge.com (William E. Davidsen Jr)
Newsgroups: comp.unix.microport,comp.unix.xenix,comp.unix.questions,comp.unix.wizards
Subject: Re: UUCP Problems
Message-ID: <10186@steinmetz.steinmetz.ge.com>
Date: 31 Mar 88 12:46:59 GMT
References: <1113@csuna.UUCP| <10126@steinmetz.steinmetz.ge.com> <175@ists>
Reply-To: davidsen@kbsvax.steinmetz.UUCP (William E. Davidsen Jr)
Organization: General Electric CRD, Schenectady, NY
Lines: 20
Keywords: UUCP XENIX

In article <175@ists> mike@ists (Mike Clarkson) writes:
>
>Very likely.  SCO defaults its port to no parity, while most other
>Unixes default to even parity.  You have 2 choices; either change the
>parity for your port to even using /etc/gettydefs, or at the IBM end,

It's even worse than that... the older version of Xenix use 7E1, while
the more recent 2.2.x series uses 8N1.

My solution, rather than change the default back to 7E1 was to create a
little program called "uu7E1" (clever, right) which resets the parity
and execs uucico. This is then made the login shell for certain ids
which don't like no parity.

The long term solution was, as you mentioned, to have the BSD machine
calling me change to no parity.
-- 
	bill davidsen		(wedu@ge-crd.arpa)
  {uunet | philabs | seismo}!steinmetz!crdos1!davidsen
"Stupidity, like virtue, is its own reward" -me