From owner-freebsd-questions Wed Aug 9 17:38:55 1995 Return-Path: questions-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id RAA07192 for questions-outgoing; Wed, 9 Aug 1995 17:38:55 -0700 Received: from ns1.win.net (ns1.win.net [204.215.209.3]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id RAA07186 for ; Wed, 9 Aug 1995 17:38:53 -0700 Received: (from bugs@localhost) by ns1.win.net (8.6.11/8.6.9) id UAA22148 for questions@freebsd.org; Wed, 9 Aug 1995 20:43:01 -0400 From: Mark Hittinger Message-Id: <199508100043.UAA22148@ns1.win.net> Subject: re: uucp dilemma To: questions@freebsd.org Date: Wed, 9 Aug 1995 20:43:01 -0400 (EDT) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 1054 Sender: questions-owner@freebsd.org Precedence: bulk > From: Steve Ames > I've been running a freebsd system using uucp for a long time now (better than > a year). I just put a new system under the old configuration and now its broke. > Main differences: > OLD NEW > 486dx66 Pentium 90 > 16450 UART 16550a UART > 'bout sums it up. Otherwise no real differences at all. > > What it does now is that outgoing UUCP seems to work fine. Incoming UUCP gets > a lot of errrors and aborts. Let me clarify that a bit... by outgoing I mean > that I dial out and deliver or pickup the packets... incoming means they call > in to send or receive packets. Pretty wierd, but thats what seems to be happeing. I wonder if you might have a double com1 problem? Some motherboards have an on-board set of com ports that respond to the com1/2 addresses. If you put in another card to do your serial i/o maybe you have some interrupt and address space collisions. It also might be that the cable for that serial port isn't handling flow control correctly. Regards, Mark Hittinger bugs@win.net