And all the scripts checking for the existing messages in log files?
Screw them, right?
That's a good point. One possible suggestion would be to submit more than
one stdmsgs.h files. One a legacy file, and one that is more consistent
from message to message.. shooting for a gradual migration.
Ultimately, I think standard messages would greatly support/simplify
scripts, especially between the myriad of ethernet drivers. Each one
reports the data slightly differently, so you're error log analysis needs
to recognize 100 or so ways of being told that the link just went down.
"David S. Miller"
<firstname.lastname@example.org To: Janice Girouard/Austin/IBM@IBMUS
> cc: Daniel Stekloff/Beaverton/IBM@IBMUS,
06/16/2003 05:27 email@example.com, Larry Kessler/Beaverton/IBM@IBMUS,
PM firstname.lastname@example.org, email@example.com,
Subject: Re: patch for common networking error messages
From: Janice Girouard <firstname.lastname@example.org>
Date: Mon, 16 Jun 2003 17:29:15 -0500
For the sake of consistency and automatic error log analysis, it might
And all the scripts checking for the existing messages
in log files? Screw them, right?
This whole idea is starting to leave a very bad taste in
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/