linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Kessler <kessler@us.ibm.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel mailing list <linux-kernel@vger.kernel.org>,
	"Andrew V. Savochkin" <saw@saw.sw.com.sg>,
	cgl_discussion mailing list <cgl_discussion@osdl.org>,
	evlog mailing list <evlog-developers@lists.sourceforge.net>,
	Rusty Russell <rusty@rustcorp.com.au>,
	Hien Nguyen <hien@us.ibm.com>,
	James Keniston <kenistoj@us.ibm.com>,
	Mike Sullivan <sullivam@us.ibm.com>
Subject: Re: [PATCH-RFC] README 1ST - New problem logging macros (2.5.38)
Date: Thu, 26 Sep 2002 11:56:34 -0700	[thread overview]
Message-ID: <3D935862.2133DEA2@us.ibm.com> (raw)
In-Reply-To: 20020924051505.GA21499@kroah.com

Greg KH wrote:
> 
> Hi,
> 
> First off, this looks much nicer than what the Driver Hardening Group
> just tried to pass off as event logging.  

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)

  parent reply	other threads:[~2002-09-26 18:52 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-24  1:55 [PATCH-RFC] README 1ST - New problem logging macros (2.5.38) Larry Kessler
2002-09-24  2:40 ` Jeff Garzik
2002-09-24  5:55   ` Rusty Russell
2002-09-24  6:11     ` Jeff Garzik
2002-09-24  6:58       ` Rusty Russell
2002-09-24  5:15 ` Greg KH
2002-09-24  5:28   ` Jeff Garzik
2002-09-26 18:56   ` Larry Kessler [this message]
2002-09-26 19:38     ` Rik van Riel
2002-09-26 20:01       ` Larry Kessler
2002-09-26 18:41         ` Rob Landley
2002-09-24  5:58 ` Greg KH
2002-09-24 16:32   ` Patrick Mochel
2002-09-24  8:36 ` Andrey Savochkin
2002-09-24  4:49 [PATCH-RFC] " Larry Kessler
2002-09-24 12:58 ` Denis Vlasenko
2002-09-24 13:59   ` Gerhard Mack
2002-09-24 22:38     ` Thunder from the hill
2002-09-24  4:56 Jeff Garzik
2002-09-24 14:04 Randal, Phil
2002-09-24 14:15 ` Sven Koch
2002-09-26 15:43 ` Alan Cox

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3D935862.2133DEA2@us.ibm.com \
    --to=kessler@us.ibm.com \
    --cc=cgl_discussion@osdl.org \
    --cc=evlog-developers@lists.sourceforge.net \
    --cc=greg@kroah.com \
    --cc=hien@us.ibm.com \
    --cc=kenistoj@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=saw@saw.sw.com.sg \
    --cc=sullivam@us.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).