From owner-freebsd-current Fri May 12 19:38:34 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id TAA21013 for current-outgoing; Fri, 12 May 1995 19:38:34 -0700 Received: from relay4.UU.NET (relay4.UU.NET [192.48.96.14]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id TAA21006 for ; Fri, 12 May 1995 19:38:32 -0700 Received: from ast.com by relay4.UU.NET with SMTP id QQypmg22198; Fri, 12 May 1995 22:38:29 -0400 Received: from trsvax.fw.ast.com (fw.ast.com) by ast.com with SMTP id AA00187 (5.67b/IDA-1.5 for uunet!FreeBSD.org!freebsd-current); Fri, 12 May 1995 19:38:29 -0700 Received: by trsvax.fw.ast.com (/\=-/\ Smail3.1.18.1 #18.1) id ; Fri, 12 May 95 21:39 CDT Received: by nemesis.lonestar.org (Smail3.1.27.1 #18) id m0sA4xA-0004w0C; Fri, 12 May 95 19:21 CDT Message-Id: Date: Fri, 12 May 95 19:21 CDT To: freebsd-current@FreeBSD.org, terry@cs.weber.edu From: uhclem%nemesis@fw.ast.com (Frank Durda IV) Sent: Fri May 12 1995, 19:21:07 CDT Subject: Re: Taylor UUCP Sender: current-owner@FreeBSD.org Precedence: bulk [0]From: uhclem%nemesis@fw.ast.com (Frank Durda IV) [0]That reminds me. Taylor UUCP 1.04 and 1.05 both deliberatly disable [0]hardware flow control (-crtscts) when it is running. You have to change [0]the UUCP source (as far as I know) to get hardware flow control to remain [0]on. This happens for incoming and outgoing UUCP sessions. [1]From: terry@cs.weber.edu (Terry Lambert) [1]This is because most systems don't handle CTS/RTS correctly prior to DCD [1]being raised on outgoing calls, and act wierd if DCD is lost while CTS [1]or RTS has been deasserted. Whatever. I was more concerned with the data part of the call, which is the point when Taylor turns this off. Nearly all of the other System V systems I have seen leave RTS/CTS active if you wanted it on. Even SCO. [0]I have to reapply this patch every time I upgrade my FreeBSD systems. [1]I'd be more comfortable if this patch became active only as a command [1]line option whose default was off. This would also make it more likely [1]to be included in the main line so that BSD doesn't have to carry it [1]around on a vendor branch. I wasn't suggesting including it *anywhere* in the production tree in its current form. Instead I was offering it as a way to fix problems that bother Taylor UUCP users every day who are using high baud modems (like Telebits or V.34). FYI, I have also gotten eight or nine letters thanking me for the immediate improvement they got (I was impressed). So maybe the change is more valuable to those of us who still have to move news and mail around via UUCP. Perhaps Ian will eventually implement something to handle this from the sys or dial file, or at least change Taylor UUCP to *not* fiddle with the settings that were set prior to it starting. But for now, that patch is a lifesaver for heavy UUCP users. Frank Durda IV |"The Knights who say "LETNi" or uhclem%nemesis@fw.ast.com (Fastest Route)| demand... A SEGMENT REGISTER!!!" ...letni!rwsys!nemesis!uhclem |"A what?" ...decvax!fw.ast.com!nemesis!uhclem |"LETNi! LETNi! LETNi!" - 1983