From owner-freebsd-current  Mon Jun 10 22:16:58 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id WAA24504
          for current-outgoing; Mon, 10 Jun 1996 22:16:58 -0700 (PDT)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id WAA24472
          for <current@FreeBSD.ORG>; Mon, 10 Jun 1996 22:16:49 -0700 (PDT)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.12/8.6.9) id PAA14272; Tue, 11 Jun 1996 15:14:57 +1000
Date: Tue, 11 Jun 1996 15:14:57 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199606110514.PAA14272@godzilla.zeta.org.au>
To: bde@zeta.org.au, nate@sri.MT.net
Subject: Re: CLOCK stuff at bootup
Cc: current@FreeBSD.ORG
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>> >(Forgive me, but I'm not clock expert, nor do I understand what all of
>> >this buys me if I have to hand-set all of these variables.)
>> 
>> Then don't ask.  The defaults work the same as before.

>Don't stick stuff in the default kernel that don't make any sense.  I

It's not in the default kernel (GENERIC or 2.1).

>It's too technical for the 'average' user, but you're making the default
>verbosity enough to peak the interest of the average user.

I hoped to pique the expertise of above-average users.

>Help me help you by making your instructions more clear please.  Don't
>assume I have a clue, then I will be more able to help you do whatever
>it is you're trying to do. :)

What I'm trying to do is get feedback about working and broken clocks
only from users who know what to look for.

Bruce