Are there any man pages for any of the system error messages?
in [General Linux]
|
Prev: Live CD to scan windows pc for a virus
Next: where is CentOS storing my hostname that it resets it on each reboot?
From: Mark Hobley on 5 Apr 2010 10:07 In comp.os.linux.misc Tony Lawrence <pcunix(a)gmail.com> wrote: > If you do anything even vaguely like that, please let me know because > I'd like to add a link to it at my http://aplawrence.com/Unixart/errors.html > post. Yes of course. I have already started numbering the error messages, although I am in the very early stages of this. I have written a basic specification on how the error numbers will look. I have also started producing library code that will be used by ernie to translate the error numbers into error messages. I also have a list of known error messages that have been encountered to date. I also have some notes against some error messages, which will probably be used to form the first man pages against the new error codes, unless I get other submissions before this happens. I haven't quite decided on a template for the manual pages yet. I'll know more when I roll out the first man page. Universal Error Numbering System: http://markhobley.yi.org/ueni/uen.html Error Message Sets: http://markhobley.yi.org/ueni/sets/index.html Sections For The Manual Pages: http://markhobley.yi.org/manpages/sections.html You can now follow me on twitter for announcements and updates: http://twitter.com/markhobley Mark. -- Mark Hobley Linux User: #370818 http://markhobley.yi.org/
From: Mark Hobley on 5 Apr 2010 10:53 In comp.unix.bsd.misc unruh <unruh(a)wormhole.physics.ubc.ca> wrote: > Because error messages are indications of errors for specific things > that you are trying to do, not errors in some sort of platonic ideal. > You try to do task A, you get and error, you look at the docs for task A > to find out what kinds of errors could occur. That is interesting. However, I have not seen this information on any of the pages that I have looked at. Also, can a user always tell, which application the error message is coming from? Take an error, such as "C++ compiler cannot create executables". This may have come from a configure script, or from a make command. Neither man configure, nor man make reveal a troubleshooter for this error message. I doubt that even the man page for g++ mentions this error. Without an error number, how would I find the relevant documentation for this? Mark. -- Mark Hobley Linux User: #370818 http://markhobley.yi.org/
From: unruh on 5 Apr 2010 11:39 ["Followup-To:" header set to comp.os.linux.misc.] On 2010-04-05, Mark Hobley <markhobley(a)hotpop.donottypethisbit.com> wrote: > In comp.unix.bsd.misc unruh <unruh(a)wormhole.physics.ubc.ca> wrote: >> Because error messages are indications of errors for specific things >> that you are trying to do, not errors in some sort of platonic ideal. >> You try to do task A, you get and error, you look at the docs for task A >> to find out what kinds of errors could occur. > > That is interesting. However, I have not seen this information on any of > the pages that I have looked at. > > Also, can a user always tell, which application the error message is coming > from? > > Take an error, such as "C++ compiler cannot create executables". This may > have come from a configure script, or from a make command. It could I suppose. It could come from random program as well. It is not a system error message that you want your man page for. Are you really going to try to tablulate all error messages from all 100000 programs that have ever been written for Linux? And keep it up to date by continuously tracking all those and all new programs and scripts ever written for Linux? > > Neither man configure, nor man make reveal a troubleshooter for this error > message. I doubt that even the man page for g++ mentions this error. > > Without an error number, how would I find the relevant documentation for this? > > Mark. >
From: Bit Twister on 5 Apr 2010 11:49 On Mon, 05 Apr 2010 15:39:53 GMT, unruh wrote: > It could I suppose. It could come from random program as well. It is not > a system error message that you want your man page for. Are you really > going to try to tablulate all error messages from all 100000 programs > that have ever been written for Linux? And keep it up to date by > continuously tracking all those and all new programs and scripts ever > written for Linux? Not to mention possible new error number/messages added to include files. :)
From: Mark Hobley on 5 Apr 2010 14:13
In comp.os.linux.misc unruh <unruh(a)wormhole.physics.ubc.ca> wrote: > It could I suppose. It could come from random program as well. It is not > a system error message that you want your man page for. Are you really > going to try to tablulate all error messages from all 100000 programs > that have ever been written for Linux? Well, I am hoping that someone will join me in this quest. I don't really want to do all of this alone. But yes, the general goal of the project is to tabulate each of the error messages. Some error messages will be duplicated and can be tied to the same reference documentation, so maybe only 90000 of those 100000 messages require entries. > And keep it up to date by > continuously tracking all those and all new programs and scripts ever > written for Linux? As time goes by, I am hoping that we shall see less "new" error messages, because the scenarios under which they occur correlate to existing documentation. Mark. -- Mark Hobley Linux User: #370818 http://markhobley.yi.org/ |