From owner-freebsd-bugs@FreeBSD.ORG  Thu Apr 29 23:30:37 2004
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 67CD016A508
	for <freebsd-bugs@hub.freebsd.org>;
	Thu, 29 Apr 2004 23:30:37 -0700 (PDT)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP id B69FF43D31
	for <freebsd-bugs@hub.freebsd.org>;
	Thu, 29 Apr 2004 23:30:28 -0700 (PDT)
	(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1])
	i3U6USFK046166	for <freebsd-bugs@freefall.freebsd.org>;
	Thu, 29 Apr 2004 23:30:28 -0700 (PDT)
	(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i3U6URVZ046165;
	Thu, 29 Apr 2004 23:30:27 -0700 (PDT)
	(envelope-from gnats)
Date: Thu, 29 Apr 2004 23:30:27 -0700 (PDT)
Message-Id: <200404300630.i3U6URVZ046165@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.org
From: Valentin Nechayev <netch@netch.kiev.ua>
Subject: Re: bin/54141: wrong behavour of cu(1)
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: Valentin Nechayev <netch@netch.kiev.ua>
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Apr 2004 06:30:37 -0000

The following reply was made to PR bin/54141; it has been noted by GNATS.

From: Valentin Nechayev <netch@netch.kiev.ua>
To: bug-followup@freebsd.org
Cc:  
Subject: Re: bin/54141: wrong behavour of cu(1)
Date: Fri, 30 Apr 2004 09:25:17 +0300

 >  There is a strange workaroung for this problem: start "cu -l cuaa0"
 >  then switch to another terminal, do "stty -crtscts </dev/cuaa0"
 >  and cu starts to work as expected (for this run only).
 
 cu sets hardflow by itself.
 
 >  It seems that cu(1) does not respect prior command 
 >  "stty -crtscts </dev/cuaia0" anymore. Or it might be a kernel bug
 >  as preliminary "stty -crtscts </dev/cuala0" does not help too.
 
 To lock a capability, set it in locking device, not unset.