From owner-freebsd-current Fri Mar 1 14:39:32 2002 Delivered-To: freebsd-current@freebsd.org Received: from mclean.mail.mindspring.net (mclean.mail.mindspring.net [207.69.200.57]) by hub.freebsd.org (Postfix) with ESMTP id 0CDCA37B405 for ; Fri, 1 Mar 2002 14:39:24 -0800 (PST) Received: from user-1120buk.dsl.mindspring.com ([66.32.47.212] helo=europa2) by mclean.mail.mindspring.net with smtp (Exim 3.33 #1) id 16gvgQ-0007OW-00; Fri, 01 Mar 2002 17:39:22 -0500 Message-Id: <3.0.6.32.20020301173731.00da4ab0@imatowns.com> X-Sender: ggombert@imatowns.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Fri, 01 Mar 2002 17:37:31 -0500 To: Cliff Sarginson , current@FreeBSD.org From: Glenn Gombert Subject: Re: more -current testers In-Reply-To: <20020301213427.GA732@raggedclown.net> References: <3C7364A5.4600F8F5@FreeBSD.org> <20020219125011.A15871@blackhelicopters.org> <3C7364A5.4600F8F5@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I have spent several months figuring how to do diskless mounts for test kernels, run debuggers from serial terminals and do remote kernel debugging with gdb, and spent lots and lots of time doing is as well. Some 'up to date' "How To's" are really needed to support this kind of debugging and testing efforts, the material in the FreeBSD manual is helpful to a point, but much 'key' information on such subjects is just not there and has to be dug out of mailing list archives and just sending e-mails to various people who have done such things in the past and ask for help, taking up their time...which could be saved with some up-to-date documentation :)) GG At 10:34 PM 3/1/2002 +0100, Cliff Sarginson wrote: >On Wed, Feb 20, 2002 at 10:56:05AM +0200, Maxim Sobolev wrote: >> Michael Lucas wrote: >> > >> > I understand that we're getting to that stage where we need more >> > -current testers. >> > >> > We all agree that the optimal thing would be to have hordes of very >> > sophisticated users who can debug problems on their own and submit >> > patches to fix all their issues. I would guess that we all also agree >> > that that's not going to happen. >> > >> > It seems that the best we can hope for is to educate some of the >> > braver users who are ready to take the next step and are willing to >> > donate some time to us. >> > >> > I'm considering doing a series of articles on testing FreeBSD-current, >> > including: setting up for kernel dumps, what to type at the debugger >> > prompt after a crash, filing a decent bug report, what to expect from >> > -current, and so on. I would also make it clear when to not bother >> > filing a bug report (i.e., "You crashed, but had no WITNESS? Sorry, >> > enable WITNESS & try again."). This would be (I suspect) three >> > articles, running about a month and a half. >> > >> > The last time I checked, I get 12-15 thousand readers for each >> > article. One half of one percent uptake would (hopefully) be quite a >> > few bug reports. >> >Has some kind of conclusion been arrived at on this ? >It has gone quiet since Feb 20th, I am definitely interested. > >-- >Regards > Cliff Sarginson -- > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > Glenn Gombert ggombert@imatowns.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message