From owner-cvs-sys  Tue Mar  4 04:05:17 1997
Return-Path: <owner-cvs-sys>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id EAA18654
          for cvs-sys-outgoing; Tue, 4 Mar 1997 04:05:17 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA18646;
          Tue, 4 Mar 1997 04:05:09 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id WAA07852; Tue, 4 Mar 1997 22:57:50 +1100
Date: Tue, 4 Mar 1997 22:57:50 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199703041157.WAA07852@godzilla.zeta.org.au>
To: ache@nagual.ru, dg@root.com
Subject: Re: cvs commit: src/sys/i386/isa clock.c
Cc: bde@zeta.org.au, cvs-all@freefall.freebsd.org,
        CVS-committers@freefall.freebsd.org, cvs-sys@freefall.freebsd.org,
        gpalmer@FreeBSD.org
Sender: owner-cvs-sys@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

>   The calibration results are not useful to 99.999% of the people who use
>FreeBSD. If they should notice that the clock isn't working correctly, then
>they can 'boot verbose' and provide the information to the developers.

Do we have 1-10 million users? :-)

The evidence may be gone on the next reboot.  Verbose messages, at least
in the message buffer, should be the default anyway, so that the messages
are available when needed.  It's too much to ask for people who have sent
an inadequate bug report to reboot, especially when the problem didn't
cause a panic.

Bruce