Date: 24 Feb 98 08:37:23 +0100 From: leifn@image.dk (Leif Neland) To: freebsd-hackers@FreeBSD.ORG Subject: errormessages Message-ID: <2d4_9802240919@swimsuit.swimsuit.roskildebc.dk>
next in thread | raw e-mail | index | archive | help
Why dont errormessages contain an unique errornumber too?
Like: "foo: Error#13: Smurf seriously overgulfed"
"foo: Error#14: Smurf somewhat undergulfed"
Then it would be easier to find the error, when somebody on the mailinglists
writes "Hey, I got this message something like the Smurf was gulfed".
An unique errornumber including the filename of the executable which generated
it is much easier to write down too...
A database of errormessages, explanations and fix'ems would be easier to
search.
Perhaps the numbers should be higher than the standard unix errornumbers to
avoid confusion.
Leif Neland
leifn@image.dk
---
|Fidonet: Leif Neland 2:234/49
|Internet: leifn@image.dk
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2d4_9802240919>