Re: dmesg verbosity [was Re: AGP bogosities]

[Diego Calleja <diegocg@gmail.com>]

El Mon, 14 Mar 2005 08:55:18 -0800,
Jesse Barnes <jbarnes@engr.sgi.com> escribió:

> We already have the 'quiet' option, but even so, I think the kernel is *way* 
> too verbose.  Someone needs to make a personal crusade out of removing 
> unneeded and unjustified printks from the kernel before it really gets better 
> though...

But people who wants to know what has been and what hasn't been detected should
start looking at sysfs, shouldn't them?. dmesg is not reliable *at all*, sometimes
when you rmmod something, it doesn't put anything in dmesg, but it did when it was
loaded, so you'll see some messaje in the printk saying "foo was loaded", but it isn't really
loaded

Personally I don't use dmesg anymore to look "what devices are being handled by the
kernel", just sysfs and /proc files. I only look at dmesg when "something goes wrong"
and it doesn't works properly. IMHO dmesg in linux is just a "debug tool" (unlike the BSDs,
who seem to have very strict rules for dmesg messages) and it's nice that it's verbose,
and it could even be "quiet" by default - people who have problems and can't look at sysfs
could add a "noquiet" boot option or run dmesg if it boots. IIRC is what solaris and other
people do by default. Why should people look at all that "horrid" debug info everytime
they boot, except when they have a problem?