From owner-freebsd-current@FreeBSD.ORG  Wed Jan 14 23:02:03 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 CA07916A4CE
	for <current@freebsd.org>; Wed, 14 Jan 2004 23:02:03 -0800 (PST)
Received: from hotmail.com (bay1-f148.bay1.hotmail.com [65.54.245.148])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 30DFF43D55
	for <current@freebsd.org>; Wed, 14 Jan 2004 23:02:02 -0800 (PST)
	(envelope-from rob_macgregor@hotmail.com)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Wed, 14 Jan 2004 23:02:02 -0800
Received: from 82.33.62.105 by by1fd.bay1.hotmail.msn.com with HTTP;
	Thu, 15 Jan 2004 07:02:01 GMT
X-Originating-IP: [82.33.62.105]
X-Originating-Email: [rob_macgregor@hotmail.com]
X-Sender: rob_macgregor@hotmail.com
From: "Rob MacGregor" <rob_macgregor@hotmail.com>
To: current@freebsd.org
Date: Thu, 15 Jan 2004 07:02:01 +0000
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <BAY1-F148n4jbOLckeK000245f0@hotmail.com>
X-OriginalArrivalTime: 15 Jan 2004 07:02:02.0046 (UTC)
	FILETIME=[79D815E0:01C3DB35]
Subject: Re: Question on quieting kernel boot
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: me@privacy.net
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Jan 2004 07:02:03 -0000

>From: Sheldon Hearn <sheldonh@starjuice.net>
>
>I think the problem is that one person's cruft is another person's
>useful info.
>
>The general solution to the problem you've pointed out is
>facility/priority logging, a'la syslog.  A kernel implementation
>probably represents a lot of work.

And what's cruft one day may be useful another (when something stops 
working).

That's why want I'm looking for is options, rather than changing the 
default.  However I hadn't considered a kernel level syslog type facility as 
a solution.  While a lot of work it probably is the best approach.

Ok, I'll go away and put my thinking hat on.

Ta

--
Rob  |  What part of "no" was it you didn't understand?

_________________________________________________________________
Stay in touch with absent friends - get MSN Messenger 
http://www.msn.co.uk/messenger