Received: (at submit) by bugs.debian.org; 20 Dec 1996 09:16:53 +0000 Received: (qmail 2769 invoked from network); 20 Dec 1996 09:16:28 -0000 Received: from gimli.Informatik.Uni-Oldenburg.DE (134.106.1.10) by master.debian.org with SMTP; 20 Dec 1996 09:16:03 -0000 Received: by gimli.Informatik.Uni-Oldenburg.DE (Smail3.1.29.1) id ; Fri, 20 Dec 96 10:15 CET Received: at Infodrom Oldenburg (/\##/\ Smail3.1.29.1 #29.10 Joey) by finlandia.Infodrom.North.DE from tapiola.Infodrom.North.DE with smtp id ; Fri, 20 Dec 96 10:15 MET Received: at Infodrom Oldenburg (/\oo/\ Smail3.1.29.1 #29.36) by tapiola.Infodrom.North.DE id ; Fri, 20 Dec 96 10:05 MET Message-Id: Date: Fri, 20 Dec 96 10:05 MET From: joey@tapiola.Infodrom.North.DE (Martin Schulze) To: submit@bugs.debian.org Subject: kerneld should not write to stdout Package: modules Version: 2.1.8-1 If you need to debug the kernel/kerneld and advice kerneld to write debug output, it is written to stdout. This is imho a bad idea and annoying esp. when the machine is far away from you. If you have to boot the machine and have debugging enabled it writes to the console, but doesn't perform a CR after each line, only an LF is performed. This is hard to reed (this paragraph, too...) Regards, Joey