Date: Mon, 16 Jul 2007 15:14:04 +0200 From: Ivan Voras <ivoras@fer.hr> To: John Baldwin <jhb@freebsd.org> Cc: freebsd-hackers@freebsd.org, freebsd-current@freebsd.org Subject: Re: Debugging times Message-ID: <469B6F1C.6020605@fer.hr> In-Reply-To: <200707160755.14498.jhb@freebsd.org> References: <f6u94s$v6o$1@sea.gmane.org> <uk5t1xa08.fsf@indorsoft.ru> <469B2787.9010302@fer.hr> <200707160755.14498.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigC9B5182C29B5F923AF200466 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable John Baldwin wrote: > It's more that we use the filesystem's timestamp as a way to validate t= he=20 > timestamp from the RTC and to do a fixup if the RTC appears to be dead.= Why not use something that doesn't depend on external factors, like kernel build time (AFAIK it's embedded somewhere - at least it's written on boot)? This way people using non-UFS file systems wouldn't get bitten.= --------------enigC9B5182C29B5F923AF200466 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGm28cldnAQVacBcgRApCLAJ9aD4S/KAIuowQ7FijtMYmpeENRNwCdHdYr zCXOTX3v05T2oISvwS4SyhQ= =/lvs -----END PGP SIGNATURE----- --------------enigC9B5182C29B5F923AF200466--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?469B6F1C.6020605>