Thanks to the following people:
grs@claircom.com
motech!owens
celeste@xs.com
tkevans@eplrx7.es.duPont.com
I took Gregg Siegfried`s suggestion and used the P_ZERO in the
chat script, and things worked the first time. Thanks.
> From grs@claircom.com Fri May 26 22:10:43 1995
> To: steve@opensys.com
> Subject: Re: 8 Bit/No Parity---now uucp fails
> X-Status:
>
> use P_ZERO in the calling chat script.
>
> As in:
>
> system Any ACU 38400 12345566 "" P_ZERO "" \d\r\d\r gin:--gin: user word: foo
>
> Gregg
>
> From tkevans@eplrx7.es.duPont.com Sat May 27 05:38:01 1995
> Subject: Re: 8 Bit/No Parity---now uucp fails
> To: steve@opensys.com
> X-Mailer: ELM [version 2.4 PL24]
> Mime-Version: 1.0
> Content-Type: text/plain; charset=US-ASCII
> Content-Transfer-Encoding: 7bit
> X-Status:
>
> Sez Steve Lee (for which I'm grateful):
> >
[original message deleted]
> >
> You can specify "P_ZERO" in the /etc/uucp/Systems file on the
> client machine. This is documented in the System and Networking
> Adminstrator's Guide, and in a lot of other manuals which tell
> you how to set up BNU (UUCP).
>
> --
> Tim Evans | E.I. du Pont de Nemours & Co.
> tkevans@eplrx7.es.dupont.com | Experimental Station
> (302) 695-9353/8638 (FAX) | P.O. Box 80357
> EVANSTK AT A1 AT ESVAX | Wilmington, Delaware 19880-0357
>
> From xs.com!celeste@stokely.mtview.ca.us Sat May 27 04:51:49 1995
> To: steve@opensys.com
> Subject: Re: 8 Bit/No Parity---now uucp fails
> X-Sun-Charset: US-ASCII
> Content-Length: 2692
> X-Status:
>
> Been there, been bitten by that. The problem is that <cr> to getty
> can be different from <cr> to login. (Crudely put, but will serve the
> purpose.)
>
> They need to change their chat to force a cr, and it will take a
> few tries to get it right. For instance, have the remote systems
> play with the login and password string this way:
>
> /etc/uucp/Systems:
>
> fred Any ACU 38400 5551212 "" \n ogin: Uthisacct ssword: mypasswd
> fred Any ACU 38400 5551212 "" \n ogin: Uthisacct\r ssword: mypasswd\n
> fred Any ACU 38400 5551212 "" \n ogin: Uthisacct\n ssword: mypasswd\n
>
> One of these 3 sets of "\r...\n" will do the trick for them. The good news
> is that once they get it set right, they shouldn't need to change it.
>
> ..Celeste Stokely, Unix System Administration Consultant, Stokely Consulting
> EMAIL: celeste@xs.com
> Voice Line: 415-967-6898 / FAX: 415-967-0160
> USMAIL Address: Stokely Consulting/211 Thompson Square/Mountain View CA 94043
> ------------------------------------------------------------------------
> If you want "Celeste's Tutorial on Solaris 2.x Modems & Terminals"
> send email to celeste@xs.com and ask for it. Latest rev is 1.3, 4/20/95
> ------------------------------------------------------------------------
>
>
> From motech!owens Sat May 27 03:12:53 1995
> To: xylan!opensys.com!steve
> Subject: Re: 8 Bit/No Parity---now uucp fails
> X-Status:
>
>
> >From omni!daemon Sat May 27 01:09:51 1995
> >Sender: omni!ra.mcs.anl.gov!sun-managers-relay
> >Date: Fri, 26 May 1995 07:13:14 -0700 (PDT)
> >From: Steve Lee <omni!opensys.com!steve>
> >Reply-To: Steve Lee <omni!opensys.com!steve>
> >Followup-To: junk
> >X-Sender: steve@pnw
> >To: sun-managers@eecs.nwu.edu
> >Subject: 8 Bit/No Parity---now uucp fails
> >Mime-Version: 1.0
> >Content-Type>: >TEXT/PLAIN>; >charset=US-ASCII>
> >Content-Length: 1374
> >
> >A couple of weeks ago I changed the way our server answers
> >its modem port from using 7 Bit/Even Parity to 8 Bit/No Parity.
> >This was required to allow SLIP and PPP from selected off-site
> >system, and was done through a change in the /etc/gettytab
> >entry (yes, this is a 4.1.3_U1 system). Since then, off-site
> >systems which call in for uucp have not been able to connect.
>
> I have a similar set up....
>
> Provided that the calling system is also a sun or running
> the same variant of uucp, all you need to do is specify
> STTY=cs8 and P_ZERO in the appropriate entry in /etc/uucp/Dialers.
>
> I'm using a USR Courier with the following Dialers entry:
>
> courier =,-, "" STTY=cs8 "" P_ZERO "" /e/patm1d/T/r
>
> the "" STTY=cs8 "" P_ZERO sequence basically says expect nothing,
> set the port to 8bits/char expect nothing then set the port to
> no parity expect nothing, then carry on with the 'normal'
> send strings....
>
> This works great for me...
>
> >
> >I've scoured the man pages/answerbook to find out if I can
> >get the port to dial out at 8 Bit/No Parity, but don't find
> >any references to uucp specifically. Interestingly, I can
> >call from the off-site systems into the main system using
> >cu and when prompted for the username, typing the username
> >and a "Return" does produce the password prompt.
>
> The basic idea is alluded to in the system/networking administration
> manual....
>
> >
> >In a word, "Help!" Any ideas on what needs to be done
> >to get uucp back up and running?
> >
> >Steven Lee OpenSystems, Inc.
> >Manager, Data Center Services 10210 NE Points Drive, Suite 110
> >steve@pnw.opensys.com Kirkland, WA 98033-7872
> >206.803.5000 x 106 Voice 206.803.5001 FAX
> >
> >
>
> ciao
>
> /mgo
>
> Mark Owens
> Network Administrator Xylan Corporation
> owens@xylan.com
>
Original Message
> From sun-managers-relay@ra.mcs.anl.gov Fri May 26 23:18:31 1995
> Sender: sun-managers-relay@ra.mcs.anl.gov
> Reply-To: Steve Lee <steve@opensys.com>
> Followup-To: junk
> X-Sender: steve@pnw
> To: sun-managers@eecs.nwu.edu
> Subject: 8 Bit/No Parity---now uucp fails
> Mime-Version: 1.0
> Content-Type: TEXT/PLAIN; charset=US-ASCII
> X-Status:
>
> A couple of weeks ago I changed the way our server answers
> its modem port from using 7 Bit/Even Parity to 8 Bit/No Parity.
> This was required to allow SLIP and PPP from selected off-site
> system, and was done through a change in the /etc/gettytab
> entry (yes, this is a 4.1.3_U1 system). Since then, off-site
> systems which call in for uucp have not been able to connect.
>
> I've been able to have the off-site systems trace the uucp
> connection (through uucico -x9) and it appears that the
> chat script that previously worked now hangs after the
> username is entered. No password prompt is seen by uucico.
> It's almost as if the ^M that was the line terminator
> when uucico saw a 7 Bit/Even Parity line is now not "good
> enough" when it sees an 8 Bit/No Parity line.
>
> I've scoured the man pages/answerbook to find out if I can
> get the port to dial out at 8 Bit/No Parity, but don't find
> any references to uucp specifically. Interestingly, I can
> call from the off-site systems into the main system using
> cu and when prompted for the username, typing the username
> and a "Return" does produce the password prompt.
>
> In a word, "Help!" Any ideas on what needs to be done
> to get uucp back up and running?
>
> Steven Lee OpenSystems, Inc.
> Manager, Data Center Services 10210 NE Points Drive, Suite 110
> steve@pnw.opensys.com Kirkland, WA 98033-7872
> 206.803.5000 x 106 Voice 206.803.5001 FAX
>
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:10:25 CDT