Xref: utzoo comp.sys.sgi:7589 comp.unix.internals:1742 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!van-bc!ubc-cs!alberta!cpsc.ucalgary.ca!deraadt From: deraadt@cpsc.ucalgary.ca (deraadt) Newsgroups: comp.sys.sgi,comp.unix.internals Subject: Re: Where does TERM get set for Telnet logins (NOT EXACTLY) Message-ID: Date: 4 Jan 91 16:03:06 GMT References: <1990Dec17.034330.27909@ccu1.aukuni.ac.nz> <1991Jan1.104335@IASTATE.EDU> <79506@sgi.sgi.com> <79769@sgi.sgi.com> Distribution: comp Organization: UofC cpsc Lines: 21 In-Reply-To: deraadt@cpsc.ucalgary.ca's message of 4 Jan 91 07:45:42 Nntp-Posting-Host: fsa In article I write: > I thought that the original discussion was that login does not support the > -h flag, and that a telnetd started with a $TERM set would result in login > and telnetd providing telnetd's $TERM in the case when the correct $TERM > could not be determined. Whoops. Mess up. I mean -p. Ie., when telnetd starts login, it is not to provide the -p flag, and the result is that login is supposed to discard the previous environment and build an environment completely anew. Getty, on the other hand, does supply -p, because getty builds part of the environment, and login is supposed to just suppliment it. Oh well. I think I'm getting religous about a BSDism in a system V group. I should run for cover.