From owner-freebsd-chat Mon Nov 18 15:27:33 2002 Delivered-To: freebsd-chat@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 778AB37B401 for ; Mon, 18 Nov 2002 15:27:32 -0800 (PST) Received: from hub.org (hub.org [64.49.215.141]) by mx1.FreeBSD.org (Postfix) with ESMTP id 31B8A43E8A for ; Mon, 18 Nov 2002 15:27:32 -0800 (PST) (envelope-from scrappy@hub.org) Received: from hub.org (hub.org [64.49.215.141]) by hub.org (Postfix) with ESMTP id 1D1E38A3586; Mon, 18 Nov 2002 19:27:28 -0400 (AST) Date: Mon, 18 Nov 2002 19:27:28 -0400 (AST) From: "Marc G. Fournier" To: Brad Knowles Cc: Anthony Atkielski , FreeBSD Chat Subject: Re: FreeBSD: Server or Desktop OS? In-Reply-To: Message-ID: <20021118192332.L19853-100000@hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, 18 Nov 2002, Brad Knowles wrote: > At 8:08 PM -0400 2002/11/17, Marc G. Fournier wrote: > > > Exactly, but if there is not sufficient support for those willing to do > > that effort, it makes it very difficult ... that's why I think there > > almost might need to be a stable-qa list that some of us can have a more > > focused ear of the developers on ... not for build related issues, only > > stability related ... if I can't build the system, I don't install it, I > > just wait a few days and try again ... > > To ensure that the signal/noise ratio is kept to reasonable > levels, the stable-qa and current-qa lists should be reserved for > people who are willing to commit extra time and resources to actually > properly debugging things (which I believe I am willing and able to > do, and sounds like you are as well), and there should be a similar > commitment from the people writing the code. I think one of the things that would really help, if at all possible, is a more compreshensive 'how to debug a kernel' document ... whenever mine crashes, first place I go is the handbook and grab as much as I know to grab, but if that could somehow be extended? For instance, the one thing I never clued into until Matt showed me was using ps/pstat against my vmcore to see how much swap was in use, and what processes were running when she crashed ... Basically, the more informed we, the debuggers/testers, can be, the easier job of it the developers, who can fix it, will have ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message