> >> 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.
Sorry. Kernel _does_ print some information (look for KERN_CRIT
etc. in sources). Severity levels are not too well set and often
missing, I know, but they are there. Feel free to fix them.
> (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)
You should worry - as it suggested that something _seriously_ wrong is
happening.
> 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?
They do have that hierarchy. Look better.
-- I'm really pavel@atrey.karlin.mff.cuni.cz. Pavel Look at http://atrey.karlin.mff.cuni.cz/~pavel/ ;-).- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu