From owner-freebsd-current@FreeBSD.ORG Thu Sep 3 05:01:54 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 62A2C106568D for ; Thu, 3 Sep 2009 05:01:54 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from kientzle.com (kientzle.com [66.166.149.50]) by mx1.freebsd.org (Postfix) with ESMTP id 36CA48FC14 for ; Thu, 3 Sep 2009 05:01:53 +0000 (UTC) Received: (from root@localhost) by kientzle.com (8.14.3/8.14.3) id n8351ro5018309; Wed, 2 Sep 2009 22:01:53 -0700 (PDT) (envelope-from kientzle@freebsd.org) Received: from dark.x.kientzle.com (fw2.kientzle.com [10.123.1.2]) by kientzle.com with SMTP id 5fi5jnpa3jupnb2h3cwhvqpqma; Wed, 02 Sep 2009 22:01:53 -0700 (PDT) (envelope-from kientzle@freebsd.org) Message-ID: <4A9F4DC1.4010002@freebsd.org> Date: Wed, 02 Sep 2009 22:01:53 -0700 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.21) Gecko/20090601 SeaMonkey/1.1.16 MIME-Version: 1.0 To: Astrodog References: <200909010931.16880.nick@van-laarhoven.org> <1251841416.1689.4458.camel@balrog.2hip.net> <200909021656.15747.nick@van-laarhoven.org> <2fd864e0909021645p735e22b8id7d41f4b5a0ee89e@mail.gmail.com> In-Reply-To: <2fd864e0909021645p735e22b8id7d41f4b5a0ee89e@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org 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: Thu, 03 Sep 2009 05:01:54 -0000 >> FreeBSD has historically been producing very limited output on dmesg. Linux >> is very noisy (ever noticed the copyright notices right in the middle of >> your list of PCI devices?). Even they have decided that they should hide >> this behind coloured 'ok/failed' texts in some distributions. > > I think this speaks more towards needing something between "Very > Quiet" and "Give me everything every developer has ever wanted to know > enough to include a print for it." Other possibilities: * Provide a per-driver control to determine verbosity. That would make it easier for developers who really do want to see "everything there is to know in my part of the world". * Put more information into the kernel buffers (and from there into dmesg) and less on the screen. That would reduce visible boot verbosity while retaining the post-hoc debugging value of dmesg(1). Cheers, Tim