Thanks for the feedback. You've asked a lot of good questions, some of
which have been answered in subsequent posts. Instead of attempting to
answer them all now, we'll make sure we take them into account as we
update and fix the original proposal. I'll answer a couple though.
> The two groups might want to
> get together to sort out which formats is the desired ones, as they are
> radically different.
We will.
>
> > * Developers, Distros, Sys Admins, etc. can simply edit the template
> > (or provide an alternate template) to control which information from
> > the problem record is displayed, how it is displayed, what language
> > it is displayed in, and can add additional information like probable
> > cause, recommended operator actions, recommended repair actions, etc.
> > ...all without requiring any changes in the device driver source code.
>
> But who is going to be doing these "translations"? Kernel log messages
> change with every release. That would be a _huge_ undertaking to
> translate them all.
I would not expect translations to be done for each and every version.
Not is the expectation that EVERY prink would be converted, only those that
report errors.
Distros could be motivated to provide translations, etc. for the kernel
versions that they base new releases on. It would just have to make
sense for them financially to translate and supplement what's in the
templates AND be an accepted/expected practice in the community (based on
some Distro feedback).
>
> I can see someone creating some job security for a long time with this
> task :)
>
And what's wrong with that ? 8)
-
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/