Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 27 Apr 2005 22:13:22 -0400
From:      jason henson <jason@ec.rr.com>
To:        cvs-all@FreeBSD.org
Subject:    Re: cvs commit: src/sys/dev/sound/usb uaudio.c uaudio.h uaudio_pcm.c
Message-ID:  <427046C2.2040903@ec.rr.com>

next in thread | raw e-mail | index | archive | help
On Wed, Apr 27, 2005 at 04:57:53PM -0400, Mathew Kanner wrote:
> On Apr 27, Julian Elischer wrote:
> > 
> > only got your email after doing the commit..
> > As I said inthe other email..
> > I think dfferently.
> > We can put it in either place (or both), but I think it's much more 
> > useful here.
> 
> 	Let's keep it here until I commit the version that does it in
> boot verbose (it's much shorter than what I remeber the PR having) The
> information will appear under boot_veborbose for that 1 time in 1000
> that you want more information about your USB device.  If people
> complain, I'll put this back.  Hope this is ok for you.

My $0.02:

Firstly, I would think that this information (or part of it) is also
useful for programs.

Secondly, dmesg(8) is unreliable in that there may be so many other
messages that the information you're looking for is not in the message
buffer anymore.

Thirdly, verbose boot is already too verbose. Let's not make it
worse. I think verbose boot should help diagnose boot problems or
device attach and/or device configure problems. Everything else
is non-critical information and should ideally be available in
some form or another when the machine has booted. Reality disagrees
with me, but it's a valid datapoint nonetheless.

FYI,

-- 
 Marcel Moolenaar	  USPA: A-39004		 marcel@xcllnt.net

There is also /var/run/dmesg.boot, shouldn't this make it reliable?



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?427046C2.2040903>