Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!munnari.OZ.AU!uunet!in1.uu.net!199.94.215.18!cam-news-hub1.bbnplanet.com!news.bbnplanet.com!panix!news.panix.com!usenet From: perry@jekyll.piermont.com (Perry E. Metzger) Newsgroups: comp.unix.bsd.netbsd.misc Subject: Re: Why no addusr? Date: 17 Feb 1997 15:55:27 -0500 Organization: Partnership for an America Free Drug Lines: 53 Message-ID: <87raif6tkw.fsf@jekyll.piermont.com> References: <none-ya023480001912962244220001@news.infi.net> <1997Feb16.104106@screwem.citi.umich.edu> <5e8v8r$ca2@camel5.mindspring.com> <DERAADT.97Feb17013838@zeus.pacifier.com> <5e977m$80@panix2.panix.com> <1997Feb17.110920@screwem.citi.umich.edu> NNTP-Posting-Host: jekyll.piermont.com X-Newsreader: Gnus v5.3/Emacs 19.32 Xref: euryale.cc.adfa.oz.au comp.unix.bsd.netbsd.misc:5432 honey@citi.umich.edu (peter honeyman) writes: > Thor Lancelot Simon writes: > > Jason and Curt both posted indicating this, and peter responded by > insisting that Jim Rees had filed bug reports. > > It turned out that this was not the case. peter, in fact, admitted this. > > no, peter admitted that jim's bug reports were not accompanied the the > right forms. There are no "forms". There is a bug reporting program. You type "send-pr" on any NetBSD machine, and the thing lets you type in a bug report. These reports get put in a tracking system so that they cannot be lost and are eventually acted upon. Random comments made to mailing lists are not the same as bug reports. If I posted here "hey, something is broken" I should have no expectation that anyone in a position to fix the thing would even necessarily see the report. "send-pr" is at least as easy to use as "mail" -- I can't see how it could have been particularly onerous to use. It is self-documenting -- no man pages to read. As it turns out, there are no bug reports, open or closed, in the database that originated with Jim or anyone else at CITI. I am sorry if Jim posted some comments about problems he was having to one of the NetBSD mailing lists or newsgroups and that they were not acted upon, but it is difficult to impossible to track reports made that way, especially when it may be some days between a bug report and the time someone has time to apply a fix. > citi switched to openbsd when we discovered that our bug reports > were being acted on there, As I do not use OpenBSD, and am unfamiliar with the troubles Jim was having, I cannot comment on whether or not they were fixed in OpenBSD. However, I must say that of the thousands of bug reports in the NetBSD PR database (which is public), most are paid attention to and closed very quickly. > notwithstanding our lack of attention to > suitly detail. (and other reasons, not germane to this flame-fest.) By the way, as for "suitly detail", I believe the bulk of the NetBSD core team doesn't wear a suit on anything like a regular basis -- nor, for that matter, do the good folks at Cygnus who built Gnats, which is what NetBSD uses for trouble tracking. You don't have to wear a suit to think that trouble reporting systems are good. I believe OpenBSD also uses send-pr and Gnats, for that matter.