Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!sdd.hp.com!apollo!apollo.hp.com!pato
From: pato@apollo.HP.COM (Joe Pato)
Newsgroups: comp.sys.apollo
Subject: Re: TERM Variable at 10.3
Message-ID: <4fac8953.20b6d@apollo.HP.COM>
Date: 7 Feb 91 16:04:00 GMT
References: <262@galileo.rtn.ca.boeing.com> <4fa32e87.20b6d@apollo.HP.COM> <4fa7e183.1bc5b@pisa.ifs.umich.edu>
Sender: root@apollo.HP.COM
Reply-To: pato@apollo.HP.COM (Joe Pato)
Organization: Hewlett-Packard Apollo Division - Chelmsford, MA
Lines: 27

In article <4fa7e183.1bc5b@pisa.ifs.umich.edu>, rees@pisa.ifs.umich.edu
(Jim Rees) writes:
|> In article <4fa32e87.20b6d@apollo.HP.COM>, pato@apollo.HP.COM (Joe
Pato) writes:
|> 
|>   The TERM variable is controlled by the entry in the /etc/ttys file.  If
|>   you look at this file you will probably find that the "term" entry for the
|>   display is set to "apollo".  This is the default setting we send out with
|>   every machine.  You should edit this entry to correspond to the display
|>   type attached to the machine.
|> 
|> I've never changed /etc/ttys, and mine lists the display type as 'apollo'. 
|> But when I log in my TERM is set to the display type that I have.  This is
|> done in the pm at process creation time.  But if you have a display type
|> that was invented after April 7, 1987, your TERM will just be "apollo."
|> 
|> I happen to think this is reasonable, although it could be better
|> documented.

Whenever you use /bin/login (e.g., via telnet or in a window or xterm)
the data in the /etc/ttys file will override any info otherwise set by 
the PM.

                    -- Joe Pato
                       Cooperative Computing Division
                       Hewlett-Packard Company
                       pato@apollo.hp.com