Re: [PATCH-RFC] README 1ST - New problem logging macros (2.5.38)

[Denis Vlasenko]

On 24 September 2002 02:49, Larry Kessler wrote:
> Jeff Garzik wrote:
> > >       }
> > >       if (!request_mem_region(pci_resource_start(pdev, 0),
> > >                       pci_resource_len(pdev, 0), "eepro100")) {
> > > -             printk (KERN_ERR "eepro100: cannot reserve MMIO
> > > region\n"); +             pci_problem(LOG_ERR, pdev, "eepro100: cannot
> > > reserve MMIO region");
> >
> > bloat, no advantage over printk
>
> the advantage is that the string, which means plenty to the developer, but
> possibly much less to a Sys Admin, can be replaced with a more descriptive
> message, in the local language, by editing the formatting template in
> user-space.  Since the printk messages were mapped directly over to the
> problem macros, then the issue here I think is how useful (or not) the
> info. is more so than what interface is used.

The problem is that printks are very easy, people won't easily switch
to any other thing if it is hard to understand/use. If you can provide
such easy interface, then ok.

Regarding translation problem: it makes life easier to admins, i.e. you
enable Linux to be used by more stupid admins :-).

This race could not be won: Universe can always produce more remarkable
idiots. Next time they will ask you "what is eepro100?" and if you say
"it's a NIC, if you have intermittent link indicator problem try to reseat
network cord..." they will ask "what is NIC and how to reseat the cord?"
(btw, they will ask that in their native language). 8-(

Maybe requiring admins to know basic English is not that bad?
--
vda