Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!philabs!cmcl2!harvard!seismo!rochester!kodak!ektools!ken
From: ken@ektools.UUCP (Kenneth J. Lester)
Newsgroups: net.bugs.uucp
Subject: Re: ULTRIX uucp vs. 4.3bsd (and others)
Message-ID: <391@ektools.UUCP>
Date: Mon, 12-May-86 16:31:33 EDT
Article-I.D.: ektools.391
Posted: Mon May 12 16:31:33 1986
Date-Received: Thu, 15-May-86 06:40:36 EDT
References: <4938@topaz.RUTGERS.EDU>
Reply-To: ken@ektools.UUCP (Kenneth J. Lester)
Distribution: net
Organization: Eastman Kodak, Dept. 47
Lines: 30
Keywords: parity

In article <4938@topaz.RUTGERS.EDU> rubin@topaz.RUTGERS.EDU (Mike Rubin) writes:
>
>It seems that ULTRIX uucp defaults to "send even parity and accept
>ONLY EVEN PARITY".  This makes it unable to converse with various
>other systems, including (it seems) 4.3bsd.  The fix: you must put
>the magic cookie "P_ZERO" in your send-expect sequence, e.g.
>	foovax Any ACU 1200 5551212 "" P_ZERO ....
>
>--Mike Rubin	Timeplex, Inc.	{topaz, philabs!wu1}!timeplex!mrubin

We were using Ultrix-32 1.1 on a VAX 750, and have made uucp connections to
various unix machines (Version 7, Sun 2.2, and System 5.2) without running 
into any parity problems.  A week ago we upgrade to Ultrix-32 1.2 and it
didn't break any of our uucp connections.  We do not use P_ZERO in our 
send-expect sequence.  In fact the uucp installation and administration 
manual for both versions state that P_ZERO is the default.

It would be helpful if you stated the exact version of Ultrix that is causing
this difficulty.

-- 
-------------------------------------------------------------------------
Ken Lester
System Administrator, Software Tools Laboratory
Product Software Engineering

USPS:   EASTMAN KODAK COMPANY, 901 Elmgrove Rd., Rochester, NY 14650
VOICE:  716 726-0322
UUCP:   {allegra, seismo}!rochester!kodak!ektools!ken
ARPA:   kodak!ektools!ken@rochester.ARPA