Alan Cox <[EMAIL PROTECTED]> writes:
> It would be a good project to add explanations to the kernel errors. The
> challenge (this is one for the perl hackers I guess) is to write a tool
> which can extract the printk/panic and a suitably marked up comment
> following it and output them into a document.
Yup, that's an interesting task. The GNU folks seem to have
had some degree of success with their national language support
by making it "easy" (for some value of "easy") to have differing
translated texts. One might envison a replacement for printk()
that looked like:
#define printk(message_id, message_text, message_description , #
substitutions) \
__printk(__message_text(message_id), substitutions)
void __printk(char *printf_style_string, ...);
char *__message_text(char *message_id); /* Look up message and return text */
printk("AlViro001", "VFS is perfect, you just don't understand it",
"This message details the characteristics of the Linux Virtual File \
System (VFS) layer, and why you shouldn't attempt to make any \
changes to it.");
and then grep across the sources for printk() usage and post-process
them to build the message repositories (translated as desired by
assorted non-US folks) and the message man pages (likewise).
Ross Patterson
Computer Associates
