> It should always honour the setting of $TERM. Make sure your network > login tool correctly propogated $TERM and a suitable value.
It does work properly for normal logins. The problem I'm complaining about is messages generated by init during boot. Either $TERM is not being set properly for /dev/console during the boot process, or the init scripts are ignoring it and just spewing ANSI terminal command sequences without checking whether the device is capable of executing them. The latter may be the case, as when I do explicitly set a $TERM of "dumb" or "tty" in the script, I still get ANSI sequences. IMHO, the Right Thing (tm) is to assume during boot that $TERM is "tty" until and unless probed and/or explicitly told otherwise. Easy enough to do in the console initialization scripts, and is just good programming practice (good software development rule 10DC: never use a hardware feature without probing for it first). I know I've given the Debian folks a ton of grief about this, but it'd be nice to fix it across the board. -- db ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
