On Thu, 2003-04-10 at 00:31, Jim Keniston[UNIX] wrote:
> Kernel messages need to be logged in English. By application of message
> catalogs or similar techniques, they can also be made available in other
> languages. Translation to other languages should be done when the log
> is viewed.
Absolutely agreed. The only case you might want to argue otherwise is
panic and very early boot messages. and even then it is questionable.
> printk(KERN_INFO "link up, %d Mbps, %s-duplex\n", speed, duplex);
> you log the format string and the values of speed and duplex as separate
> attributes in the event log. If/when you compute a hash, it's on the
> format string (and possibly on the function name and/or source-file
> name, to provide more context).
One of the problems is extracting the format string and other data.
Making the log hold
<6>%s: carrier dropped and smashed on the floor[U001]eth0
is in itself not hard and a big step forward.
> - If we use 32-bit hash codes, there's a real chance of different
> messages
There are less than 65536 files each of which is less than 65536 lines
long, so it seems that a properly chosen automated index ought to be
collision free ?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Apr 15 2003 - 22:00:21 EST