From owner-freebsd-current@FreeBSD.ORG  Wed Jan 14 22:46:53 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 EC5BB16A4CE
	for <current@freebsd.org>; Wed, 14 Jan 2004 22:46:53 -0800 (PST)
Received: from axl.seasidesoftware.co.za (axl.seasidesoftware.co.za
	[196.31.7.201])	by mx1.FreeBSD.org (Postfix) with ESMTP id 48CB243D5F
	for <current@freebsd.org>; Wed, 14 Jan 2004 22:46:52 -0800 (PST)
	(envelope-from sheldonh@starjuice.net)
Received: from sheldonh by axl.seasidesoftware.co.za with local (Exim 4.30;
	FreeBSD)	id 1Ah1HF-000FZE-Bb; Thu, 15 Jan 2004 08:46:49 +0200
Date: Thu, 15 Jan 2004 08:46:49 +0200
From: Sheldon Hearn <sheldonh@starjuice.net>
To: me@privacy.net
Message-ID: <20040115064649.GG59417@starjuice.net>
Mail-Followup-To: me@privacy.net, current@freebsd.org
References: <BAY1-F112AaWZ3DWh2400013cf0@hotmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <BAY1-F112AaWZ3DWh2400013cf0@hotmail.com>
User-Agent: Mutt/1.5.4i
cc: current@freebsd.org
Subject: Re: Question on quieting kernel boot
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
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 06:46:54 -0000

On (2004/01/14 17:17), Rob MacGregor wrote:

> Looks like both options are extremes of what I'm after.  I'm really looking 
> for a quiet option, to cut out the cruft.  However, as there is a verbose 
> boot option that might give me a starting point for a quieter boot option.

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.

Ciao,
Sheldon.