> Is there any non-botchy way to make this go away?  A stty kluge, or
> something?  I've heard rumors telnetd -k may fix it, but I'd prefer to
> avoid that, as I have perfectly respectable telnet clients everywhere except
> work.

If telnetd -k fixes it, then you have no choice.  However, the way I fix
it without gunking up reasonable telnet clients is by running telnetd -k
on port 22 (which is otherwise unused) and just remembering to type "telnet
jfwhome.funhouse.com 22" on the Suns at work (very easy to remember if you
use an alias :-).