The problem, of course, is that the ANSI sequences (on an x86 machine
and others with an "ansi mapped display") make the boot-up process look
"pretty" by reporting success/failure of each stage in a "clear" fashion.
That being said, for the x86 versions, doing an
ssh [EMAIL PROTECTED] "cd /etc/init.d && ./named
restart"
(Yes, yes, I know there are better ways to do this) no ANSI sequences
are returned.
All right, so that's using SuSE 8.2 and it's not on a zSeries.
-soup
--------------------
John R. Campbell, Speaker to Machines (GNUrd) {813-356|697}-5322
Adsumo ergo raptus sum
MacOS X: Because making Unix user-friendly was easier than debugging
Windows.
Red Hat Certified Engineer (#803004680310286)
IBM Certified: IBM AIX 4.3 System Administration, System Support
----- Forwarded by John Campbell/Tampa/IBM on 10/21/2004 12:20 PM -----
David Boyes
<[EMAIL PROTECTED] To: [EMAIL PROTECTED]
e.net> cc:
Sent by: Linux on Subject: Re: [LINUX-390] Sigh.. is it
really too much trouble to check the terminal
390 Port ty pe?
<[EMAIL PROTECTED]
IST.EDU>
10/21/2004 11:13
AM
Please respond to
Linux on 390 Port
> 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
