From owner-freebsd-current@FreeBSD.ORG Wed Mar 24 17:16:54 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4AFC116A4CF for ; Wed, 24 Mar 2004 17:16:54 -0800 (PST) Received: from saturn.criticalmagic.com (saturn.criticalmagic.com [68.213.16.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id E775343D45 for ; Wed, 24 Mar 2004 17:16:53 -0800 (PST) (envelope-from richardcoleman@mindspring.com) Received: from mindspring.com (titan.criticalmagic.com [68.213.16.23]) by saturn.criticalmagic.com (Postfix) with ESMTP id 246FE3BD2A; Wed, 24 Mar 2004 20:16:53 -0500 (EST) Message-ID: <40623305.7080102@mindspring.com> Date: Wed, 24 Mar 2004 20:16:53 -0500 From: Richard Coleman Organization: Critical Magic, Inc. User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Garance A Drosihn References: <4061E990.4000703@alumni.rice.edu> <20040324234650.GA57375@xor.obsecurity.org> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: current@freebsd.org cc: Kris Kennaway Subject: Re: LOR status page? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: richardcoleman@mindspring.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Mar 2004 01:16:54 -0000 Garance A Drosihn wrote: > At 3:46 PM -0800 3/24/04, Kris Kennaway wrote: > >> On Wed, Mar 24, 2004 at 02:03:28PM -0600, Jon Noack wrote: >> > Would it be helpful to put up a web page with all known lock >> > order reversal false positives (or better yet all known lock >> > order reversals with a status indication)? This would allow >> > people to check there before reporting, saving everyone time. >> >> Clearly we need to do something to stop people reporting the same >> non-bugs every day, the problem is that it needs to be somewhere >> people are likely to check. Maybe a pointer to your proposed >> webpage in UPDATING will help. > > > Could we do something so we don't PRINT the false-positives? If > we're about to turn 5.x-current into 5.x-stable, then it is not > good to tell users "Here are a bunch of error messages that you > should just ignore". At least in my experience, what happens is > that users are much more likely to ignore *all* error messages. > > I have no idea what would need to be done, of course. I'm just > uneasy at telling users to ignore scary-looking error messages. > > I do agree that a web page saying exactly which ones to ignore > would be better than expecting end-users to figure that out by > scanning the mailing lists... I'm assuming WITNESS et al. will be turned off by default for 5.3-stable. So most users will never see these messages. And I doubt a webpage will stop folks from reporting this. Maybe a big note at the top of UPDATING would help. Richard Coleman richardcoleman@mindspring.com