Path: utzoo!attcan!uunet!know!sdd.hp.com!wuarchive!decwrl!ucbvax!mindcrf.UUCP!karish
From: karish@mindcrf.UUCP (Chuck Karish)
Newsgroups: comp.unix.aix
Subject: Re: Telnet negotiation - Not a defect: a feature!
Summary: Not a unique AIX feature
Message-ID: <9010121513.AA07533@mindcrf.mindcraft.com>
Date: 12 Oct 90 15:13:28 GMT
References: <1990Oct8.192405.19439@ux1.cso.uiuc.edu> <3814@awdprime.UUCP> <1990Oct11.172158.16069@ux1.cso.uiuc.edu>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: Mindcraft, Inc.
Lines: 35

In article <1990Oct8.192405.19439@ux1.cso.uiuc.edu>
resnick@cogsci.uiuc.edu (Pete Resnick) wrote:
>But any time I log in over telnet, my terminal
>type gets set to whatever is in /etc/ports.

Later, he added:

>If there is no entry in /etc/ports, it sets it to 'dumb'.
>
>Dumb.

UNIX systems maintain information about the terminal type in the
shell, not in the terminal driver.  Telnet itself doesn't know
what the terminal type is, and therefore can't do the negotiation.
It's been done this way since telnet was first provided on BSD
systems, as far as I know; AIX behavior does not differ from
historical practice.

The rlogin protocol does propagate the $TERM variable from the
environment.  This is the only environment variable from the
local shell that's provided to the remote shell.

When your terminal type comes up as `dumb', there are two things
you can have your session initialization script (.cshrc, .profile, etc.)
do:

- Prompt you to fill in the correct terminal type, and set it
  in $TERM (and $term, in csh).

- Run a program to probe the terminal for an identification code;
  many terminals can report what type they are.
-- 

	Chuck Karish		karish@mindcraft.com
	Mindcraft, Inc.		(415) 323-9000