Date: Tue, 27 May 1997 01:05:36 +1000 From: David Nugent <davidn@labs.usn.blaze.net.au> To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Cc: gary@systemics.com (Gary Howland), bugs@FreeBSD.ORG Subject: Re: /etc/ttys is broken Message-ID: <199705261505.BAA00648@labs.usn.blaze.net.au> In-Reply-To: Your message of "Mon, 26 May 1997 15:59:55 %2B0200." <19970526155955.BO13767@uriah.heep.sax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
> > The latest release of /etc/ttys is broken. Do a diff with an old release > > and the problem will be obvious. > > You could have been more specific. It's not obvious to me what you > mean. It wasn't obvious to me either. I looked, and didn't have a clue as to what Gary was talking about. It appears that he failed to read the relevent manpages. > Btw., David, i think `dialup' is a poor choice. The probably most > ``generic'' TERM entry that could be used is vt100. It constitutes > something like a least common denominator. People having something > else want to adjust their $TERM anyway, and for the remaining 90 %, > it's a good default. The "dialup" term type is a "magic" value. This is the compromise I worked out which causes isdialupttp() to do its stuff, just like "network" is the default for ptys (although the problem isn't present for ptys, since $TERM is typically set over a network login). As a compromise, I suggest something like: [ "x$TERM" = "x" -o "x$TERM" = "xdialup" ] && eval `tset -s "?vt100"` in /etc/profile, and if (!?$TERM || "x$TERM" == "xdialup") then eval `tset -s "?vt100"` endif in /etc/csh.login by default (this is similar to what has to be done for network logins where no TERM is passed). Or if an interactive query is not desired, then just set the variable as desired. Perhaps login(1) can take care of the translation. Only one additional statement is required. Another option would be to change the /etc/ttys to use the new keyword which designates the dialup ttys explicitly as "dialup" and use vt100. However, this isn't backwards compatible with older systems (neither is using "dialup" as the term type, but at least this is more logical to folks who upgrade without reading manpages). The 'problem' was not considered a serious one when committed because people ALWAYS have to edit their ttys for use with dialup anyway, even if only to simply enable the lines in question. They would normally read the manpage first, right? :-) Ok, maybe I'm being too hopeful. In any case, using "dialup" here is not really an error. It causes login to correctly log dialup connections - and you've just reminded me that I haven't yet committed other patches which make use of this. Regards, David David Nugent - Unique Computing Pty Ltd - Melbourne, Australia Voice +61-3-9791-9547 Data/BBS +61-3-9792-3507 3:632/348@fidonet davidn@freebsd.org davidn@blaze.net.au http://www.blaze.net.au/~davidn/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199705261505.BAA00648>