Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!isavax.isa.com!cjbsys!cliffb
From: cliffb@cjbsys.bdb.com (cliff bedore)
Newsgroups: comp.unix.xenix.sco
Subject: Re: rlogin (and/or /bin/login) under SCO Xenix and TCP/IP
Message-ID: <1991Jan13.000706.15034@cjbsys.bdb.com>
Date: 13 Jan 91 00:07:06 GMT
References: <778@tiamat.fsc.com>
Organization: BDB Systems
Lines: 28

In article <778@tiamat.fsc.com> jim@tiamat.fsc.com (Jim O'Connor) writes:
>I have recently discovered that when doing an "rlogin" from hostA to
>hostB (where hostA is any TCP/IP machine, and hostB is an SCO Xenix
>machine, running TCP/IP 1.0.1h), that hostB does not correctly set
>TERM to whatever value it was on hostA.  In all cases, TERM is always
>set to "unknown" by the SCO machine.
>
>Am I missing something obvious, or is SCO's rlogind/login combo
>broken?
>
>Thanks for any help.
>--jim
>------------- 
>James B. O'Connor			jim@tiamat.fsc.com
>Ahlstrom Filtration, Inc.		615/821-4022 x. 651

It's broken on mine also.  I have inserted the following line in my .login
which at least offers me my favorite terminal if the system doesn't know what
the terminal is.


set term = (`tset -m ansi:ansi -m :\?ansi -r -S -I -Q`)


(replace ansi with your favorite terminal.)


Cliff