> > I have to say I've wished several times that there was a central > > location for message documentation in Linux. Kernel panic? Segfault? > > Modprobe diagnostics? I recompiled a kernel and started getting silly > > diagnostics about a "system map" whenever I ran ps. Took me awhile to > > figure out, mostly 'cause the message meaning was unobvious to the > > neophyte. > > (Google 8)) > > > The messages-and-codes manuals are one-stop-shopping for information > > about messages that you don't normally see, but which beg some > > explanation. > > We don't have one, nor I suspect the structure to create such a thing. I > can see its value but it assumes a much more military mindset than the free > software world has, as well as a lot fewer ISV's, even though I'm sure the > quake "game over" message-and-code entry would be worth a read.
If you and Linus lead the way there's some prospect of others following, at least wrt the kernel. In the mainframe world, 3rd-party vendors (and even many shops) have followed the practice because they see its value. -- Cheers John Summerfield Microsoft's most solid OS: http://www.geocities.com/rcwoolley/ Note: mail delivered to me is deemed to be intended for me, for my disposition.
