From owner-freebsd-current@FreeBSD.ORG Fri Sep 4 10:08:50 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DE180106566B for ; Fri, 4 Sep 2009 10:08:50 +0000 (UTC) (envelope-from peterjeremy@acm.org) Received: from mail10.syd.optusnet.com.au (mail10.syd.optusnet.com.au [211.29.132.191]) by mx1.freebsd.org (Postfix) with ESMTP id 6F3E88FC15 for ; Fri, 4 Sep 2009 10:08:50 +0000 (UTC) Received: from server.vk2pj.dyndns.org (c122-106-217-45.belrs3.nsw.optusnet.com.au [122.106.217.45]) by mail10.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id n84A8lXT026958 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 4 Sep 2009 20:08:48 +1000 X-Bogosity: Ham, spamicity=0.000000 Received: from server.vk2pj.dyndns.org (localhost.vk2pj.dyndns.org [127.0.0.1]) by server.vk2pj.dyndns.org (8.14.3/8.14.3) with ESMTP id n84A8lwG013343 for ; Fri, 4 Sep 2009 20:08:47 +1000 (EST) (envelope-from peter@server.vk2pj.dyndns.org) Received: (from peter@localhost) by server.vk2pj.dyndns.org (8.14.3/8.14.3/Submit) id n84A8l8p013342 for freebsd-current@freebsd.org; Fri, 4 Sep 2009 20:08:47 +1000 (EST) (envelope-from peter) Date: Fri, 4 Sep 2009 20:08:47 +1000 From: peterjeremy@acm.org To: FreeBSD CURRENT Mailing List Message-ID: <20090904100847.GA13167@server.vk2pj.dyndns.org> References: <200909010931.16880.nick@van-laarhoven.org> <1251841416.1689.4458.camel@balrog.2hip.net> <200909021656.15747.nick@van-laarhoven.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="vtzGhvizbBRQ85DL" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://members.optusnet.com.au/peterjeremy/pubkey.asc User-Agent: Mutt/1.5.20 (2009-06-14) Subject: Re: Reducing noise in dmesg output X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Fri, 04 Sep 2009 10:08:50 -0000 --vtzGhvizbBRQ85DL Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2009-Sep-03 12:39:04 +1200, James Butler wr= ote: >This seems like an important distinction - the information which needs >to be available with dmesg and the information best shown to the user >at startup are not necessarily the same. Agreed. And some rc.d scripts are also overly verbose - starting a system with 150 virtual interfaces takes a significant amount of time via a serial console. > The hypothetical "average >user" probably wouldn't care if there were *no* kernel messages shown >on startup. Whilst they mightn't care about the current probe/attach messages, it is very reassuring for the kernel to show that it is actually doing something. > The Xubuntu box I'm writing this from shows only GRUB >messages before the login prompt on tty1, and only service startup >messages on tty8 Solaris is similar - leading to some nailchewing when rebooting after a change: Does nothing being reported on the console for 2 minutes mean that the kernel has gone off into limbo or it is just slowly grinding through *something*? Whilst SIGINFO helps once userland starts, I would not be comfortable with a system that reported nothing between the boot loader and login prompts. --=20 Peter Jeremy --vtzGhvizbBRQ85DL Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (FreeBSD) iEYEARECAAYFAkqg5y8ACgkQ/opHv/APuIfr1QCbB1yDVhegaHupo3j9G0duznHR /uoAoIJKvXnuBtwXW0R5kFoT9dOSRMxV =SL8P -----END PGP SIGNATURE----- --vtzGhvizbBRQ85DL--