Date: Fri, 14 Nov 2003 12:53:59 +0700 From: Eugene Grosbein <eugen@kuzbass.ru> To: Bruce Evans <bde@zeta.org.au> Cc: freebsd-bugs@FreeBSD.org Subject: Re: bin/54141: wrong behavour of cu(1) Message-ID: <3FB46DF7.1525E251@kuzbass.ru> References: <200311140350.hAE3oL30030201@freefall.freebsd.org> <20031114155242.J6133@gamplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Bruce Evans wrote: > > On Thu, 13 Nov 2003, Eugene Grosbein wrote: > > > 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). > > Is this with the old cu (from Taylor uucp) or the current cu (which > is tip warmed over)? I do not know, really. I just use stock cu(1) that is installed by make installworld. I just observe broken POLA in recent FreeBSD versions. > > 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 flag off, it must be turned off in the initial state port > (before the port is opened) and locked off by turning it (strictly, > its lock bit) _on_ in the lock state port. I try to run stty on cuaia0 and cuala1 before the start of cu. It does not help. Eugene Grosbein
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3FB46DF7.1525E251>