Re: Event logging vs enhancing printk

[Martin J. Bligh]

> As I understand, Linus accepts new features only if they are improving
> kernel  in some vital area significantly (for example, Ingo's new
> scheduler).

I think that's more true of 2.4 than 2.5, but a change should indeed 
make some improvement to be accepted. What seems to be more vital
is that the cost:benefit ratio is advantageous ... much of the
discussions that Larry and I were having were oriented to keeping
the cost very low indeed ... if you didn't turn on event logging,
the cost would be pretty much 0 (just those macro unwraps).

> You'll need to show that "enhanced" printk/evlog is significant
> improvement  and is worth the trouble. That won't be easy.

Having worked in Customer service for a long time on high end
systems, I know that having accurate error logging is critical
to fast problem diagnosis. Look at the other extreme which people
like Microsoft drift towards ... I hate it when you get error
messages like "Error. Something is wrong somewhere".

If the open source methodology of "many eyes fix bugs" is to work
as well as possible, we need to help those eyes to see as clearly
as possible.

M.