>Number:         1930
>Category:       lib
>Synopsis:       termcap bug? term=linux breaks telnet, tput, vi
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    lib-bug-people (Library Bug People)
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Jan 11 12:35:01 1996
>Last-Modified:
>Originator:     Jonathan Stone
>Organization:
Stanford Distributed Systems Group
>Release:        1995-12-22
>Environment:
	
System: NetBSD Reno.DSG.Stanford.EDU 1.1A NetBSD 1.1A (NEWCONF) #3: Thu Jan 11 00:14:48 PST 1996 jonathan@Reno.DSG.Stanford.EDU:/usr/src/sys/arch/pmax/compile/NEWCONF pmax


>Description:
	Telnetting to a NetBSD/pmax current system with user-land
	installed from -current as at 1995-12-22), from a non-NetBSD
	system supporting telnet environment-variable options
	(vendor Unix with ave Borman's telnetd installed) causes the
	NetBSD telnetd to coredump. Changing the telnet client's
	environment (to say, vt100 or ansi) before telnetting
	works avoids the coredump.
	
	On a NetBSD system as above, with the terminal environment
	variable set to "linux", vi goes into an infinite loop
	before ever painting the first screen.

	On a NetBSD system as above, with the terminal environment
	variable set to "linux", clear (tput clear) coredumps.

	I conjecture this is a termcap data or termcap library bug,
	but I could be wrong.
		
	
>How-To-Repeat:
	see above.
>Fix:
	 setting "term=vt100" or "term=ansi" is a partial work-around,
	but causes incorrect tty updates in some apps, due to
	tabbing and other differences.
>Audit-Trail:
>Unformatted: