Subject: install/35566: shark sysinst unusable with serial console
To: None <install-manager@netbsd.org, gnats-admin@netbsd.org,>
From: None <root@garbled.net>
List: netbsd-bugs
Date: 02/08/2007 07:30:00
>Number:         35566
>Category:       install
>Synopsis:       shark sysinst unusable with serial console
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    install-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Feb 08 07:30:00 +0000 2007
>Originator:     Tim Rightnour
>Release:        NetBSD 4.0_BETA2 200702040000Z
>Organization:
	
>Environment:
	
	
System: NetBSD polaris.garbled.net 3.0 NetBSD 3.0 (GENERIC) #0: Mon Dec 19 01:04:02 UTC 2005 builds@works.netbsd.org:/home/builds/ab/netbsd-3-0-RELEASE/i386/200512182024Z-obj/home/builds/ab/netbsd-3-0-RELEASE/src/sys/arch/i386/compile/GENERIC i386
Architecture: arm
Machine: shark
>Description:
	When installing via sysinst over a serial console, the .profile
sets the TERM to pc3.  When this hits an xterm, it turns the screen red,
and beeps uncontrollably at you, making it impossible to type.  After beating
my head on the keyboard a few times, I finally managed to break out of sysinst
and set the term to xterm, and I was able to use sysinst.
	
>How-To-Repeat:
Boot netbsd installer via a serial console on a shark.  Be horrified.
	
>Fix:
src/distrib/shark/instkernel/ramdisk/dot.profile
probably should change pc3 to vt100?
	

>Unformatted: