From owner-freebsd-doc Tue Oct 17 10:33:46 2000 Delivered-To: freebsd-doc@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id A72F837B4F9 for ; Tue, 17 Oct 2000 10:33:44 -0700 (PDT) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e9HHXBA64330; Tue, 17 Oct 2000 10:33:11 -0700 (PDT) (envelope-from jkh@winston.osd.bsdi.com) To: peter@sysadmin-inc.com Cc: "'Jason C. Wells'" , freebsd-doc@FreeBSD.ORG Subject: Re: How To's In-Reply-To: Message from "Peter Brezny" of "Tue, 17 Oct 2000 13:23:52 EDT." <000201c0385f$05d88b60$47010a0a@fire.sysadmininc.com> Date: Tue, 17 Oct 2000 10:33:11 -0700 Message-ID: <64326.971803991@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > short step by step "here's how to get it running" documentation would do me > a lot of good. The obvious problem is that the documentation for FreeBSD is written just like its code - by volunteers. Most volunteers are also not tremendously motivated to write docs unless it's because they're frustrated enough with the state of some bit of documentation to either improve or write it from scratch. That state of frustration generally doesn't occur but once, when initially grappling with a problem just as you are now. Unfortunately, most people who work through issues like this don't stop to write up their experiences and thus leave a paved road for others to follow, they simply sigh with relief and move on to the next problem. You see the catch-22 in this situation? :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message