From owner-freebsd-hackers  Wed Dec 28 06:39:59 1994
Return-Path: hackers-owner
Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id GAA18475 for hackers-outgoing; Wed, 28 Dec 1994 06:39:59 -0800
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.9/8.6.6) with ESMTP id GAA18463; Wed, 28 Dec 1994 06:39:49 -0800
Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id BAA30737; Thu, 29 Dec 1994 01:35:38 +1100
Date: Thu, 29 Dec 1994 01:35:38 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199412281435.BAA30737@godzilla.zeta.org.au>
To: freebsd-fs@freebsd.org, freebsd-hackers@freebsd.org,
        julian@jules.DIALix.oz.au
Subject: Re: DEVFS on FreeBSD 2.0
Cc: freebsd-current@freebsd.org
Sender: hackers-owner@freebsd.org
Precedence: bulk

>1/ at device probe time, 'time' has not been initialised.. so any devices
>that are placed into the devfs at boot time end up with creation times
>of Jan 1 1970.. (time.tv_sec == time.tv_usec == 0).
>Is there a reason that the RTC can't be read earlier?

I've just been looking at the clock initializaton order.  I moved
initialization of the RTC later :-).  It's still before the RTC date
is read, but after all the non-clock devices have been initialized.
There's nothing to stop reading it earlier, but if the RTC is on
local time then it's hard to adjust it earlier.  It could be adjusted
at mountroot() time using a value read from the disk.

Bruce