> On 03 Dec 1998 16:25:16 +0100, Jes Sorensen writes:
>
> > We've had this discussion before, about a year ago I think, forget it
> > once and for all, please.
>
> I think having messages appear in the sysadmin's native language has
> merit. The front line for Linux support is moving away from this
> list.
This subject has been beaten to death on this list, several times. All of
the kernelspace solutions proposed are bloaty and exceptionally
inefficient to keep consistent. And there is effectively _ZERO_ desire by
the core developers to try to maintain such a beast.
If you really want kernel messages translated, hack dmesg and syslogd to
do the translation. The set of kernel messages is finite, and userspace
translation bloat is much more bearable than kernelspace. If that's just
not good enough and you really really really really really really want all
the printk()'s in your native language, create and maintain your own
patch, just don't expect it to get into the mainstream kernel.
Once the system has booted, the kernel shouldn't normally have much to say
anyway, and if it does, it is much more useful to this list in its present
form. Concentrate on internationalizing userspace (glibc, gnome, etc),
it's much more useful.
Adam
-- Your lives aren't small, but \\ Adam Davenport Bradley, Grad Student you're living them in a small \\ Boston University Computer Science way. Live openly and expansively! \\ artdodge@cs.bu.edu 353-8921/MCS211 II Cor 6:11-13 (The Message) <>< \\ http://www.netwinder.org/~artdodge
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/