From owner-freebsd-doc Thu Nov 8 11:23:50 2001 Delivered-To: freebsd-doc@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 794B937B405 for ; Thu, 8 Nov 2001 11:23:15 -0800 (PST) Received: (from mwlucas@localhost) by blackhelicopters.org (8.9.3/8.9.3) id OAA10223 for doc@freebsd.org; Thu, 8 Nov 2001 14:23:14 -0500 (EST) (envelope-from mwlucas) Date: Thu, 8 Nov 2001 14:23:14 -0500 From: Michael Lucas To: doc@freebsd.org Subject: finding stuff in documentation Message-ID: <20011108142314.A10189@blackhelicopters.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="KsGdsel6WgEHnImy" Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --KsGdsel6WgEHnImy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Folks, At one point, several months ago, I was looking at a problem-solving mechanism for FreeBSD. Unfortunately, my book contract got in the way. I've had time to reconsider this issue, and I think I've narrowed it down considerably. (My original solution would have taken a huge amount of my time and been maintainable only by yours truly, or some other poor loser with no life.) As a user, when I have a problem with something I don't want to ask on a mailing list or call a vendor. I want to look up the error, find out what it means, fix it, and get on with life. Right now, we encourage people to look up their errors in the FAQ, Handbook, articles, and mailing list archives. This is a lot of places to look, but we have no choice. I frequently have to click through several different pages of messages to find what I really want. Attached please find a first stab at addressing this issue: a FreeBSD "error code" index. It's an extra chapter that goes through the FAQ and lists every entry in alphabetical order. It's alpha quality, questionable markup and ancestry, but it compiles so I'm shipping it out for comments. Some errors appear in multiple areas, or are described in different sections of the FAQ. IMHO, these might indicate areas where the FAQ could use some cleanup, rearranging, or merging. A decent index would also help us manage the content of the Handbook and FAQ. Is there any DocProj interest in having this? Shall I drop it now, change, or continue? ==ml -- Michael Lucas mwlucas@blackhelicopters.org http://www.blackhelicopters.org/~mwlucas/ Big Scary Daemons: http://www.oreillynet.com/pub/q/Big_Scary_Daemons --KsGdsel6WgEHnImy Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=error-index *** en_US.ISO8859-1/books/faq/book.sgml-dist Thu Nov 8 07:46:11 2001 --- en_US.ISO8859-1/books/faq/book.sgml Thu Nov 8 14:09:27 2001 *************** *** 12342,12347 **** --- 12342,12688 ---- + + + + Michael + Lucas + +
mwlucas@blackhelicopters.org
+ + + + + Errors Index + + FreeBSD system errors are listed here, in alphabetical + order. This is not an encyclopedic list of errors, merely those + that appear in the FreeBSD FAQ and Handbook. + + Some error messages have device names in front of them. + These errors could affect any number of devices, so look for the + error without the device name. + + + + + archsw.readin.failed + + + + See this + FAQ. + + + + + bad sector table not + supported + + + + See this + FAQ. + + + + + + brkadrint, Illegal Host Acces at seqaddr + 0x0 + + + + See this + FAQ. + + + + + + calcru: negative time + + + + See this + FAQ. + + + + + + can't change attributes + + + + See this + FAQ. + + + + + + can't find libc.so.X.0 + + + + See this + FAQ. + + + + + + CMAP busy + + + + See this + FAQ. + + + + + + Couldn't open console + + + + See this + FAQ. + + + + + + Device not configured + + + + See this + FAQ if you're using a CDROM. + + + + + + ed1: timeout + + + + See this + FAQ. + + + + + + file: table is full + + + + See this + FAQ. + + + + + + Incorrect super block + + + + See this + FAQ if you're using a CDROM. + + + + + + KDENABIO failed (Operation not + permitted) + + + + See this + FAQ. + + + + + + mail loops back to myself + + + + This is a Sendmail problem. See this FreeBSD FAQ for a + brief explanation. See the Sendmail + FAQ for more information + + + + + + Missing Operating System + + + + See this FAQ. + + + + + + nlist failed + + + + See this + FAQ. + + + + + + No route to host + + + + If you're using &man.ppp.8;, see this FAQ. + + + + + + panic: can't mount root + + + + See this + FAQ. + + + + + + panic: kmem_map too small + + + + See this + FAQ. + + + + + + pcm0 not found + + + + See this + FAQ. + + + + + + Permission denied + + + + If this happens with network operations, see this + FAQ. + + + + + + Read error + + + + See this FAQ + and this FAQ + if it happens at boot. + + + + + + root: not found + + + + See this + FAQ. + + + + + + signal 11 + + + + See this FAQ. + + + + + + socksys + + + + See this + FAQ. + + + + + + stray IRQ + + + + See this FAQ. + + + + + + unknown: <PNP0303> can't assign + resources + + + + See this + FAQ. + + + + + + you are not in the correct group to su + root + + + + See this + FAQ. + + + + + Acknowledgments --KsGdsel6WgEHnImy-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message