Organizing kernel messages
Posted Oct 1, 2010 18:58 UTC (Fri) by giraffedata
Parent article: Organizing kernel messages
Rather than a message manual to find out what a kernel message means, I'd prefer that the kernel just say what it means.
Message manual technology goes back to a time when disk space and memory were so expensive that the OS couldn't afford to display more than a code; paper and operator time were cheaper.
There is still an obvious bias on the part of many software developers toward making computers tight-lipped, giving just a hint as to what might be the problem when something fails. But there's really no reason the kernel can't be more user friendly.
Having informative messages also removes much of the need to find the line of code that issued the message, as that's usually an attempt to find out what the kernel was trying to say.
And with detailed error messages, I think searching the code or the web for the text would be as easy as searching for an arbitrary message identifier.
to post comments)