2011-10-04 On Unix systems programs should be quiet if things go as expect- ed. Some well-known violators of this rule are make, configure scripts (and tex). The importance of being quiet shows up at once if you use `make -s' and `sh configure -q'. I'm not getting tired of telling that make has serious design failures; not being quiet by default is one of them. For configure applies the same as for tex: Nobody reads these tons of output -- they're just disturbing. If one is interested, he'll look into the log file *afterwards*. Maybe these tools better should have been created at times when line printers were still common. ;-) http://marmaro.de/lue/ markus schnalke