-----BEGIN PGP SIGNED MESSAGE-----

Just wondering, has someone been fiddling with the clock-slowdown
problem?  At any rate, I'm having a new problem with the clock here.

Before, the clock would be set correctly when I booted NetBSD and
would fall behind the longer NetBSD ran.  (I know about the problem
with clock interrupts.)  However, when I rebooted into the MacOS, the
clock was up-to-date.

Now, it seems that whatever time loss I suffer under NetBSD carries
into the clock value stored in PRAM, and the slowdown shows up in the
MacOS.  Not a horrible problem, as I can always reset the clock with
the Network Time control panel, but that does require dialing up for
me.  (And yes, I could do it by hand, but I like that even less.)

Has something changed in the code?  Am I losing my mind?

Scott Kaplan
sfkaplan@cs.utexas.edu
Finger me for my PGP key

-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQCVAwUBMIb0mfh1zxMpPoRtAQH9MAP/SHzhmr2NFIbHUDhbrGEZ+W6Mo9S//IL+
Ah2Y+YweShWLuNeWp0fUDYXyRa0knhFwiAM8p98Fp54iuZ8QHejx0gKRxFVWPsVj
GqjiH0ax4vNy/fGRjgCceoYfpD8NsaOQoqycLEydXk4AhO5A2zHnbQsHppvCEjkj
vLAqwiGm+3U=
=f66G
-----END PGP SIGNATURE-----