From owner-freebsd-advocacy Thu Jul 1 1:16:28 1999 Delivered-To: freebsd-advocacy@freebsd.org Received: from relay04.netaddress.usa.net (relay04.netaddress.usa.net [204.68.24.184]) by hub.freebsd.org (Postfix) with SMTP id DF2EF14CB4 for ; Thu, 1 Jul 1999 01:16:25 -0700 (PDT) (envelope-from jesus.monroy@usa.net) Received: (qmail 14437 invoked from network); 1 Jul 1999 08:16:25 -0000 Received: from www0a.netaddress.usa.net (204.68.24.30) by outbound.netaddress.usa.net with SMTP; 1 Jul 1999 08:16:25 -0000 Received: (qmail 16511 invoked by uid 60001); 1 Jul 1999 08:16:21 -0000 Message-ID: <19990701081621.16510.qmail@www0a.netaddress.usa.net> Received: from 204.68.24.30 by www0a via web-mailer() on Thu Jul 1 08:16:21 GMT 1999 Date: 1 Jul 99 01:16:21 PDT From: Jesus Monroy To: Terry Lambert Subject: Re: [Re: [Re: [Re: [Re: [Re: [Re: My FreeBSD Experience ]]]]]] Cc: advocacy@FreeBSD.ORG X-Mailer: USANET web-mailer () Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-advocacy@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry Lambert wrote: > > 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. > = The system needs a revision, but unfortunaly I took a vow of silence for the next seven days. We can pick this up then, if you like. > > 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. > = There are many solutions. But again on 7 day hold. --- "I'd rather pay for my freedom than live in a bitmapped, = pop-up-happy dungeon like NT." http://www.performancecomputing.com/features/9809of1.shtml ____________________________________________________________________ Get free e-mail and a permanent address at http://www.netaddress.com/?N=3D= 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-advocacy" in the body of the message