Kirk Corey writes:
> Can anyone give me a quick run-down (or pointer to more info) on
> what breaks without the clock.c patch?  Judging by the man page, it
> only affects things that want to measure CPU time used, right?

No. This is the code for inittodr(9) and resettodr(9).

What breaks without it? Well, we corrected a (minor) bug a few days
ago that might make some real time clocks unhappy. This patch
basically deals with the fact that we were ignoring the century byte
in the NVRAM before, which is perfectly safe to do, but isn't
"perfectly correct".

> I just want to make sure all my boxes won't start beeping at
> midnight in 400-some days; it might spoil my annual Guy Lombardo
> fest.

There are doubtless going to be some small fixes between now and then
that you are going to want to install. If/when 1.3.3 comes out, it
should have some.

Perry