From owner-freebsd-advocacy Wed Jun 30 16:31:20 1999 Delivered-To: freebsd-advocacy@freebsd.org Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (Postfix) with ESMTP id D59BC15453 for ; Wed, 30 Jun 1999 16:31:05 -0700 (PDT) (envelope-from tlambert@usr09.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id QAA26385; Wed, 30 Jun 1999 16:31:03 -0700 (MST) Received: from usr09.primenet.com(206.165.6.209) via SMTP by smtp01.primenet.com, id smtpd026359; Wed Jun 30 16:30:55 1999 Received: (from tlambert@localhost) by usr09.primenet.com (8.8.5/8.8.5) id QAA10390; Wed, 30 Jun 1999 16:30:54 -0700 (MST) From: Terry Lambert Message-Id: <199906302330.QAA10390@usr09.primenet.com> Subject: Re: [Re: [Re: [Re: [Re: [Re: My FreeBSD Experience ]]]]] To: jesus.monroy@usa.net (Jesus Monroy) Date: Wed, 30 Jun 1999 23:30:54 +0000 (GMT) Cc: seth@freebie.dp.ny.frb.org, jesus.monroy@usa.net, tlambert@primenet.com, advocacy@FreeBSD.ORG In-Reply-To: <19990630164442.12266.qmail@nwcst322.netaddress.usa.net> from "Jesus Monroy" at Jun 30, 99 09:44:42 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-advocacy@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I guess you want me to resort to that retarted'pr' system > for reporting bugs. Albeit the current defacto standard, > my posting was noted and correct by the documentation > team in less than 48hrs. Why so soon? Can't tell you, > ask them. That's "retarded 'pr' system". My guess as to the speed is that it's a result of sending email instead of using the 'pr' system. For what it's worth, I can't get the 'sendpr' stuff to work from my freebsd box behind the corporate firewall because it's apparently overly anal about reverse DNS. > Currently, errors in the documentation are constantly > creeping in because fixes (or changes) are made > to the base utility set, or the parts they > use (ie. command-line flags). This in turn does > not get commited to documentataion until the > documentation error is reported or the programmer > who may the (possible) error figures this out. > > In any case, it's a real lack of communication > between the documentation team, the core team > or freebsd-hackers in general. > > Where is the root of the problem? I don't know. > Can this be solved? I don't know. > Well this problem continue to manifest itself > at irregular times and without warning? > Yes, it's a real daemon. It's possible to resolve. The engineering technique is called "literate programming". There was apparently a nice talk about it at Usenix, with someone building a kernel using the technique to allow them to publish an example. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-advocacy" in the body of the message