Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!rpi!uupsi!sunic!ugle.unit.no!lise.unit.no!arnej
From: arnej@Lise.Unit.NO (Arne Henrik Juul)
Newsgroups: comp.unix.admin
Subject: Re: How could I set term at login
Keywords: tset, .login
Message-ID: <1991Feb23.173043.3526@ugle.unit.no>
Date: 23 Feb 91 17:30:43 GMT
References: <BUSSIERE.91Feb19194243@ganymede.DMI.USherb.CA> <476@bria> <1991Feb21.022452.18693@msuinfo.cl.msu.edu>
Sender: news@ugle.unit.no
Reply-To: arnej@solan1.solan.unit.no
Organization: Norwegian Institute of Technology
Lines: 47

At our site we use the tset program. This is not as
transparent to users as it might have been, but it works
better with all those strange terminal types and different
machines and the telnet-ing around that we do all the time.

This means that at most initial logins, tset asks the
users which terminal he has (probably you would want to
use vt100 as the default) like this:

TERM = ( vt100 ) 

and you may answer with just return or with 'vt200' if
that is better, or even with 'dumb' if it's some
braindamaged old terminal...

When you telnet or rlogin later on, things will normally
be quite OK without extra input.

Relevant things from our /local/skel/all.login:

if ( ! $?TERM ) setenv TERM '?unknown'
if ( "$TERM" == network   \
   ||  "$TERM" == dumb    \
   ||  "$TERM" == unknown \
   ||  "$TERM" == su      ) then
	setenv TERM '?unknown'
endif

set noglob
set ttynam=`tty`
switch ( `tty` )
	case /dev/console:
	case /dev/tty[pqr]*:
		eval `tset -s -r -Q $TERM`
	breaksw
	default:
		eval `tset -s -r -Q ?$TERM`
endsw
unset noglob



Regards, Arne H. Juul, system administrator solan.unit.no

arnej@lise.unit.no   -- internet mail please        -- hacker -
Arne.Juul@unit.no    -- X/400 mail for sadists      --    I   -
juul@norunit.bitnet  -- bitnet mail if you have to. --  hope  -