Path: utzoo!attcan!uunet!husc6!uwvax!rutgers!mit-eddie!uw-beaver!cornell!batcomputer!itsgw!steinmetz!vdsvax!barnett@vdsvax.steinmetz.ge.com
From: barnett@vdsvax.steinmetz.ge.com (Bruce G. Barnett)
Newsgroups: comp.unix.questions
Subject: Re: using set term in the .login file
Message-ID: <5762@vdsvax.steinmetz.ge.com>
Date: 12 Oct 88 10:50:32 GMT
References: <1139@fredonia.UUCP> <1341@midas.UUCP>
Sender: barnett@vdsvax.steinmetz.ge.com
Reply-To: barnett@steinmetz.ge.com (Bruce G. Barnett)
Organization: GE Corp. R & D, Schenectady, NY
Lines: 26
In-reply-to: mbennett@midas.UUCP (Mike Bennett)

In article <1341@midas.UUCP>, mbennett@midas (Mike Bennett) writes:
>	     tty | grep "ttyd[12]" >/dev/null
>	     if ( $status == 0 ) then
>		set term=vt52
>	     else
>		set term=(term type at school)
>	     endif
>

If you want to automatically set up your terminal, and if you have tset,
then use the information that should be available. There are two
pieces of information that can be used. The baud rate and the terminal type
associated with that port. If the terminal type is wrong, get the 
system mangler to fix it.

Let's assume the terminal type on the prt is 'network', and your baud
rate is 2400 at home, and greater than 2400 at work.

Try this in your .login file:
----------
set noglob
eval `tset -Q -s -m 'network@2400:?vt52' -m 'network>2400:?vt100' $term`
unset noglob

Also, when you rlogin, the terminal type is correct. Don't change it.
--