Date: Thu, 3 Oct 1996 11:35:18 -0400 (EDT) From: Matt Braithwaite <m-braithwaite@sjca.edu> To: joerg_wunsch@uriah.heep.sax.de Cc: freebsd-bugs@freebsd.org Subject: Re: suggested patch to tab initialization in tset/set.c Message-ID: <199610031535.LAA12487@whorfin.sjca.edu> In-Reply-To: <199610031317.PAA26567@uriah.heep.sax.de> from "J Wunsch" at Oct 3, 96 03:17:29 pm
next in thread | previous in thread | raw e-mail | index | archive | help
J Wunsch writes: > > As Matt Braithwaite wrote: > > > lines. immediately after all of that is printed, however, the > > cursor is moved *back up* to the 24th line of the display, and > > printing continues from there. however, after login, stty > > returns the right window size, and no programs assume an 80x24 > > window. so the only real problem is corruption of the motd > > before the user gets a chance to read it. the jumping of the > > cursor to the 24th line occurs with every invocation of tset > > that i tried. > > I never realized what this tset mess might be good for at all. It's > annoying at best, and does wrong things like in your case at worst. > It's usually the first thing i'm killing in my .login/.profile. > > The TERM variable is already initialized well from within /etc/ttys, > or passed down from the telnet remote peer. I would vote for killing > this beast from the default .login/.profile templates. i'm not so sure about this. i might just be nostalgic, because i have a few real terminals sitting around the house (one is an ADM3---definitely NOT vt100 compatible!), but it really gives me a warm fuzzy to have tset around to kick my terminal when i login. in practice, i have to acknowledge that you're right---just doing a setenv TERM works out to be all the terminal initialization i ever need. but terminals are weird and mysterious to me, and since not everybody is using a modern telnet program yet, i turn ignorantly to the security of having tset around to handle whatever intricacies may be lurking. i might also add parenthetically that i have seen instances where the TERM variable doesn't seem to propagate correctly. i don't know enough to say why. at the very least, i hazard a guess that it won't work if you're telnetting from a non-unix system. :-) i guess the bottom line for me is that there are still sufficient oddball cases to make having vocal, in-your-face terminal initialization at login the Right Thing. > On the same matter, the default TERM type for serial lines should IMHO > be `vt100', since this is a way better one than the useless `unknown'. > There are a few terminals around that don't do vt100 emulation, but > sysadmins who are bothered by this will adjust the settings anyway. well, you can also cover that with tset -m, of course. -- Matt Braithwaite m-braithwaite@sjca.edu http://www.sjca.edu/ph/m-braithwaite HAVE *YOU* EXPORTED A CRYPTO SYSTEM TODAY? --> http://dcs.ex.ac.uk/~aba/x.html #!/usr/local/bin/perl -s-- -export-a-crypto-system-sig -RSA-in-3-lines-PERL ($k,$n)=@ARGV;$m=unpack(H.$w,$m."\0"x$w),$_=`echo "16do$w 2+4Oi0$d*-^1[d2% Sa2/d0<X+d*La1=z\U$n%0]SX$k"[$m*]\EszlXx++p|dc`,s/^.|\W//g,print pack('H*' ,$_)while read(STDIN,$m,($w=2*$d-1+length($n||die"$0 [-d] k n\n")&~1)/2)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199610031535.LAA12487>