>> for each function). It's compact and unambiguous and will probably never be
>> adapted for Linux 8-)
> Fortunately.
Well, but perhaps some notion of error locality and severity would be a
good idea? It looks to me as if the kernel messages have no imposed
structure, and sometimes messages are produced that causes unecessary
concern -- i.e. an information message is taken as a critical error.
(See the example posted here recently, the kernel reports some kind of
ext2 error, and although the error shouldn't have happened, the user
clearly don't need to worry about data lossage)
As is well known, syslog segregates into debug, notice, warn, error and
the like - should kernel messages be sorted into a similar (the same)
hierarchy? Even if it is just a format imposed on the strings in an
informal manner?
~kzm
-- If I haven't seen further, it is by standing in the footprints of giants- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu