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: <14234@mimsy.UUCP>
Date: 29 Oct 88 04:26:16 GMT
References: <1139@fredonia.UUCP> <140@iquery.UUCP> <76@usl-pc.usl.edu> <1542@maccs.McMaster.CA>
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 29

>In article <14180@mimsy.UUCP> I noted that
>>[Annex terminal servers] 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.

In article <1542@maccs.McMaster.CA> dan@maccs.McMaster.CA (Dan Trottier)
writes:
>This still doesn't really solve the problem. Being a university there
>is no way we can tell what terminals people will be using.

For dialups, no; but for lines in offices?  You would not bring in a
different terminal each week; the wires running to the terminal server
are attached to only one terminal, and that terminal has a type.  The
type field needs changing only when the terminal attached to that port
of that server is changed.

At any rate:
>Do your Annex boxes also provide rudementary name service? We have a
>Develcon box that works quite well but it doesn't name serve.

The Annexes will use either IEN116 name service or BIND/named.  IEN116
is outdated and is provided mainly for backward compatibility; Encore
includes an IEN116 server that simply does a gethostbyname(), in case you
are still using host tables (or---blech---yp before named).
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163)
Domain:	chris@mimsy.umd.edu	Path:	uunet!mimsy!chris