>Number:         4405
>Category:       bin
>Synopsis:       sysinst coredump without termcap
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    bin-bug-people (Utility Bug People)
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Fri Oct 31 10:20:29 1997
>Last-Modified:
>Originator:     Gregory McGarry
>Organization:
Queendland University of Technology
>Release:        31 Oct 1997
>Environment:
	
System: NetBSD ernie.sprc.qut.edu.au 1.2G NetBSD 1.2G (ERNIE) #24: Mon Sep 29 08:34:51 PDT 1997 gmcgarry@ernie.sprc.qut.edu.au:/usr/src/sys/arch/pmax/compile/ERNIE pmax


>Description:

/sbin/sysinst coredumps when run without TERM set.  This can be
problematic given that the termcap is not always available in
miniroots and diskimages due to its size.

I think it's a bug that sysinst coredumps when run without TERM set.
Normal usage is to run it from a script which probably asks the user
for a tty-type and sets TERM. Even so, sysinst should print a friendly
message and exit cleanly. could you send a PR about that, too?

>How-To-Repeat:

Unset the TERM variable.

>Fix:
	
>Audit-Trail:
>Unformatted: