From owner-freebsd-current  Sat May 13 23:02:20 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id XAA24203
          for current-outgoing; Sat, 13 May 1995 23:02:20 -0700
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id XAA24197
          for <current@freebsd.org>; Sat, 13 May 1995 23:02:15 -0700
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id QAA16423; Sun, 14 May 1995 16:00:06 +1000
Date: Sun, 14 May 1995 16:00:06 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199505140600.QAA16423@godzilla.zeta.org.au>
To: hsu@clinet.fi
Subject: Re: misc/403: FreeBSD 1-compiled tcsh, bash and zsh binaries dump on vt102
Cc: current@FreeBSD.org
Sender: current-owner@FreeBSD.org
Precedence: bulk

>>Number:         403
>>Category:       misc
>>Synopsis:       FreeBSD 1-compiled tcsh, bash and zsh binaries dump on vt102

>>Description:

>	bash, zsh and tcsh print "Termcap entry too long" when setting
>terminal type to vt102 (or larger like vt220).  I don't know when this
>changed and why, I recompiled the shells on FreeBSD 2 and they work
>now.

Some termcap entries are very long.  In current libraries, tgetent() is
more careful to discard junk (mostly spaces) so that the termcap entries
are smaller than the braindamaged 1024 byte limit .  Old binaries use old
libraries so some termcap entries are larger than the limit.

>>Fix:
>	
>Recompile the stuff.  I guess this isn't dangerous, just wondering
>what has changed and will it affect other programs too (none noticed
>yet)?

The termcap entries are now more complete.

Bruce