Path: utzoo!utgpu!water!watmath!clyde!att!gargoyle!tank!mimsy!chris
From: chris@mimsy.UUCP (Chris Torek)
Newsgroups: comp.unix.questions
Subject: Re: using set term in the .login file
Keywords: vt52
Message-ID: <14180@mimsy.UUCP>
Date: 27 Oct 88 00:36:28 GMT
References: <1139@fredonia.UUCP> <140@iquery.UUCP> <76@usl-pc.usl.edu>
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 22

In article <76@usl-pc.usl.edu> jpd@usl-pc.usl.edu (DugalJP) writes:
>tset is fine when each port has a known terminal type connected to it.
>The file (in BSD4.2) /etc/ttytype gives the correspendence, which tset
>can test.  However, at USL we have a network that randomly picks a port
>such that we don't know in advance which terminal type is going to be
>used. ...

This is one reason we bought Annex terminal servers rather than (eg)
Bridge boxes:  Annexes support the rlogin protocol, and that protocol
allows the terminal type to be passed in.  The Annex boxes can be
configured to pass a particular terminal type by default.  Thus, the
information that was once in /etc/ttytype for direct lines is now in
configuration files for the Annexes serving our building.

They really are nice boxes, and the 4.0 software fixes the output flush
bug that has plagued Emacs users since 4.2BSD.

Disclaimer: I own Annex along with all of Massachusettes.  (Boy will
they be surprised!)  :-)  :-)
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163)
Domain:	chris@mimsy.umd.edu	Path:	uunet!mimsy!chris