Date: Mon, 11 Mar 2002 18:26:05 +1100 (EST) From: Bruce Evans <bde@zeta.org.au> To: <kalts@estpak.ee> Cc: Robert Watson <rwatson@FreeBSD.ORG>, <current@FreeBSD.ORG> Subject: Re: Serial break into debugger broken from 'cu' on -CURRENT? Message-ID: <20020311181940.X5606-100000@gamplex.bde.org> In-Reply-To: <20020310164640.GA21339@myhakas.estpak.ee>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 10 Mar 2002, Vallo Kallaste wrote: > work. The other thing I noticed was that -current cu handles speed > switch differently, e.g.: > stable: cu -l /dev/cuaa1 -9600 works well > current: cu -l /dev/cuaa1 -9600 will connect to cuaa0 not > cuaa1.. -s 9600 will work however. > What I recall is that some time back uucp was shaken out of base > system and cu also, cu's functionality was folded back to tip. > Stable indeed has different tip and cu binaries, in -current there's > hard link. The -current cu is a crock of tip. One of the bugs in it is that "cu -l /dev/foo" doesn't use the default line speed for /dev/foo; it enforces 9600. This is bug for bug compatible with the V7 cu except for the unusably slow speed of 9600. For perfect brokenness, the default speed should be 300. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020311181940.X5606-100000>