From owner-freebsd-current@FreeBSD.ORG Wed Mar 24 17:24:25 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 3760A16A4CF for ; Wed, 24 Mar 2004 17:24:25 -0800 (PST) Received: from smtp1.server.rpi.edu (smtp1.server.rpi.edu [128.113.2.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id E191E43D2F for ; Wed, 24 Mar 2004 17:24:24 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp1.server.rpi.edu (8.12.8/8.12.8) with ESMTP id i2P1OOHB017562; Wed, 24 Mar 2004 20:24:24 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <40623305.7080102@mindspring.com> References: <4061E990.4000703@alumni.rice.edu> <20040324234650.GA57375@xor.obsecurity.org> <40623305.7080102@mindspring.com> Date: Wed, 24 Mar 2004 20:24:23 -0500 To: richardcoleman@mindspring.com From: Garance A Drosihn Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: CanIt (www . canit . ca) cc: current@freebsd.org Subject: Re: LOR status page? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list 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:24:25 -0000 At 8:16 PM -0500 3/24/04, Richard Coleman wrote: >Garance A Drosihn wrote: >>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. Ah. True. I'm used to running with it (on i386, at least). >And I doubt a webpage will stop folks from reporting this. Maybe >a big note at the top of UPDATING would help. Too many "big notes" at the top of UPDATING, and people's eyes will glaze over and they won't read any of it. Particularly if that big note is for some event that most users won't see. A small note, with a URL, would be more likely to work, I think. Or change the error message to include that URL. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu