From owner-freebsd-current Tue Aug 22 22:48:21 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id WAA12147 for current-outgoing; Tue, 22 Aug 1995 22:48:21 -0700 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id WAA12137 for ; Tue, 22 Aug 1995 22:48:13 -0700 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id PAA05299; Wed, 23 Aug 1995 15:43:31 +1000 Date: Wed, 23 Aug 1995 15:43:31 +1000 From: Bruce Evans Message-Id: <199508230543.PAA05299@godzilla.zeta.org.au> To: freebsd-current@freefall.FreeBSD.org, jc@irbs.com Subject: Re: CLOCAL and CRTSCTS in -current and -stable Sender: current-owner@FreeBSD.org Precedence: bulk >I upgraded an old 1.1.5.1 system to -stable a few days ago and had >trouble convincing cu to talk to a port that only has TX and RX. >I had to stop cu and turn off crtscts to get cu to output. Input >works OK. Once I understood the problem, I tried the locking/initial >mechanism but -crtscts would not stick. This part of the driver hasn't changed since 1.1.5. >-current from last month cu defaults to: >cflags: cread cs8 -parenb -parodd hupcl clocal -cstopb -crtscts -dsrflow > -dtrflow -mdmbuf >-stable from last week: >cflags: cread cs8 -parenb -parodd hupcl -clocal -cstopb crtscts -dsrflow > -dtrflow -mdmbuf This must be with -current utilities and a -stable kernel (the -stable stty doesn't report -dsrflow). Applications should be compatible, howver. >Has cu changed or have the kernel defaults changed? Is the >locking/initial scheme broken in -stable? No bugs are known. Devices names have changed since 1.1.5, so a 1.1.5 script to set the locks would probably not work now. Bruce