Date: Thu, 29 Apr 2004 23:30:27 -0700 (PDT) From: Valentin Nechayev <netch@netch.kiev.ua> To: freebsd-bugs@FreeBSD.org Subject: Re: bin/54141: wrong behavour of cu(1) Message-ID: <200404300630.i3U6URVZ046165@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200404300630.i3U6URVZ046165>