From owner-freebsd-advocacy Wed Jun 30 9:45:36 1999 Delivered-To: freebsd-advocacy@freebsd.org Received: from nwcst322.netaddress.usa.net (nwcst322.netaddress.usa.net [204.68.23.67]) by hub.freebsd.org (Postfix) with SMTP id C7E2615537 for ; Wed, 30 Jun 1999 09:45:20 -0700 (PDT) (envelope-from jesus.monroy@usa.net) Received: (qmail 12267 invoked by uid 60001); 30 Jun 1999 16:44:42 -0000 Message-ID: <19990630164442.12266.qmail@nwcst322.netaddress.usa.net> Received: from 204.68.23.67 by nwcst322 via web-mailer() on Wed Jun 30 16:44:42 GMT 1999 Date: 30 Jun 99 09:44:42 PDT From: Jesus Monroy To: Seth , Jesus Monroy Subject: Re: [Re: [Re: [Re: [Re: [Re: My FreeBSD Experience ]]]]] Cc: Terry Lambert , 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 Seth wrote: > = > = > On Wed, 30 Jun 1999, Jesus Monroy wrote: > = > > Should you have problems with this statement, my opinions > > are of record and can be found at: > > = > > http://minnie.cs.adfa.oz.au/cgi-bin/newsread?12953 > > = > = > To quote from your 17 March 1993 post referenced above: > = > "I have been told more than once, by many people, from afar as = > well as in > person, that my utterances welcome detraction and criticism." > = > So I see people had the same objections to your posts back in 1993 = > as I do now. > = Welcome to the club. > This still doesn't address my original claim. You've reported that = > 15% of > the man pages have errors in them, and also disputed another person's > claim that the manpages are a strength. What are you doing to resolve = > the situation? = > 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. > I refer you to your recent post: > = > > May notes I see, in the code and occasionaly in man(1) > > pages are just wrong. Mind you I not going to run > > down these daemons I just don't have the energy for > > a fight like that. = > = 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. Do you feel yelling at the programers or docuementers trying to find out where this problem is? I certainly don't have the energy for this. > as well as to the GNATS database, where an originator search for = > "Monroy" turns up no matches for any open or closed PR's. > = And you won't. The system is worse than fixable. It has not active responsibility. I watch bugs go from open->closed to closed->open and back again. The system does note entail qualifiable or = referencable documentation. Thereby the same = documentation will be re-hash and re-corrected. If you have a suggestion on how to fix that, I'm all ears. --- "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