Getting the message from the kernel
Posted Jul 2, 2007 9:19 UTC (Mon) by alext
In reply to: Getting the message from the kernel
Parent article: Getting the message from the kernel
Besides the error message is already going to have to be unique and therefore
anyone capable of looking at the code meaningfully won't have much trouble locating it.
The big use must be to allow external full explanations to exist that allow admin's etc to apply any known changes to config that get around the problem.
And as the start of the thread suggested, why is there so much resistance to potentially having something as simple as a call with a string and that string having a unique ID attached? It sounds like Linus being a bit precious rather than treating it like just adding a new hook to the code base for others to use in documenting behavior.
to post comments)