Date: Mon, 17 Jul 1995 17:33:39 +1000 From: Bruce Evans <bde@zeta.org.au> To: mpp@legarto.minn.net, terry@cs.weber.edu Cc: bde@zeta.org.au, hackers@freebsd.org Subject: Re: FS root mount handling discrepancy Message-ID: <199507170733.RAA23493@godzilla.zeta.org.au>
next in thread | raw e-mail | index | archive | help
>Each *_mountroot routine should call inittodr, since that routine >is used to establish the system clock from the real time clock >at boot time. The argument to inittodr is the value the clock is set >to if the RTC cannot be read for some reason. I think inittodr() should be called much earlier. It doesn't need a root file system to work on systems with a suitable clock. >Something else interesting I noticed was the the APM routines call >inittodr to reset the system clock to the RTC after a resume >from a suspend, however they call it with a value of zero. >No big deal, but on the off chance that the RTC somehow died >during that interval, the time would warp back to 1/1/70. >Probably calling it with something like: > inittodr(time.tv_sec) >would be better, since the clock would just start again from >its last setting before the suspend. It should probably do this if its arg is 0 or -1. Bruce
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199507170733.RAA23493>