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 02:29 In comp.os.linux.misc despen(a)verizon.net wrote: > markhobley(a)hotpop.donottypethisbit.com (Mark Hobley) writes: > >> Does anyone know of any repositories containing man pages for system error >> messages? I am looking for pages that document error messages and resolution. > > Man pages aren't organized that way, nor should they be. Why don't you think that man pages should be organized this way? Mark. > Look instead at the documentation for the APIs. So are you saying that whenever a user gets an error message on the screen, she should start looking at the various APIs? > Each of the APIs in libc has a man page. I will look at these of course. > Again, wrong way to go about it. Ok. How do you think this should be done? > How about working with an existing documentation project: > http://tldp.org/authors/ I specifically need documentation for error messages. Whenever an error message occurs on the screen, I need to be able to pull up the documentation for it (I don't really want to start looking through API documentation here.) I am always looking to work with other authors who have similar mission objectives in mind, of course. Who do you suggest? Mark. -- Mark Hobley Linux User: #370818 http://markhobley.yi.org/
From: Mark Hobley on 5 Apr 2010 02:44 In comp.os.linux.misc Bit Twister <BitTwister(a)mouse-potato.com> wrote: > That documentation would be pretty impressive. Resolution would depend > on what was going on at the time, where. > Example: Unable to open file. I am actually working on some infrastructure for this. Each error message will be given a unique number, that can then be used to locate the corresponding documentation. http://markhobley.yi.org/ueni/index.html I was hoping that someone would jump start this by pointing me to some man pages. Some of my own notes will probably be converted into manual pages too, as time permits. I am also going to wade through that lot that you posted. Thanks. Mark. -- Mark Hobley Linux User: #370818 http://markhobley.yi.org/
From: Bit Twister on 5 Apr 2010 07:38 On Mon, 5 Apr 2010 07:44:22 +0100, Mark Hobley wrote: > I am also going to wade through that lot that you posted. Thanks. It is not just errno.h files. Pick a function, say getaddrinfo. man getaddrinfo and note the SYNOPSIS #include lines. Use locate to find netdb.h, then cat /usr/include/netdb.h Note: you have h_errno error codes and the getaddrinfo function errors. You will also have the other SYNOPSIS #include files plus any includes inside each include .h file.
From: Tony Lawrence on 5 Apr 2010 07:50 On Apr 5, 2:44 am, markhob...(a)hotpop.donottypethisbit.com (Mark Hobley) wrote: > In comp.os.linux.misc Bit Twister <BitTwis...(a)mouse-potato.com> wrote: > > > That documentation would be pretty impressive. Resolution would depend > > on what was going on at the time, where. > > Example: Unable to open file. > > I am actually working on some infrastructure for this. Each error message > will be given a unique number, that can then be used to locate the > corresponding documentation. > > http://markhobley.yi.org/ueni/index.html > > I was hoping that someone would jump start this by pointing me to some man > pages. Some of my own notes will probably be converted into manual pages too, > as time permits. > > I am also going to wade through that lot that you posted. Thanks. > > Mark. > > -- > Mark Hobley > Linux User: #370818 http://markhobley.yi.org/ 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.
From: unruh on 5 Apr 2010 09:40
On 2010-04-05, Mark Hobley <markhobley(a)hotpop.donottypethisbit.com> wrote: > In comp.os.linux.misc despen(a)verizon.net wrote: >> markhobley(a)hotpop.donottypethisbit.com (Mark Hobley) writes: >> >>> Does anyone know of any repositories containing man pages for system error >>> messages? I am looking for pages that document error messages and resolution. >> >> Man pages aren't organized that way, nor should they be. > > Why don't you think that man pages should be organized this way? 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. > > Mark. > >> Look instead at the documentation for the APIs. > > So are you saying that whenever a user gets an error message on the screen, > she should start looking at the various APIs? > >> Each of the APIs in libc has a man page. > > I will look at these of course. > >> Again, wrong way to go about it. > > Ok. How do you think this should be done? > >> How about working with an existing documentation project: >> http://tldp.org/authors/ > > I specifically need documentation for error messages. Whenever an error > message occurs on the screen, I need to be able to pull up the documentation > for it (I don't really want to start looking through API documentation here.) > > I am always looking to work with other authors who have similar mission > objectives in mind, of course. Who do you suggest? > > Mark. > |