In message <[EMAIL PROTECTED]>, Bruce Evans writes: >On Thu, 6 Feb 2003, Andrey A. Chernov wrote: > >> On Wed, Feb 05, 2003 at 23:44:08 +0100, [EMAIL PROTECTED] wrote: >> > >> > >2) Feb 6 01:36 (boot time) >> > >3) Feb 6 04:36 (+3 TZ future jump) >> > >> > These timestamps have been touched, and the clock has made a 3 hour >> > jump either forward or backward at some point. >> > >> > The problem is the clock jump, not DEVFS. >> >> Clock jump happens as it supposed when adjkerntz(8) corrects machine clock >> back to GMT via various CPU_* sysctl's. Could touched DEVFS stamps be >> fixed back to something useful in the same sysctl code too? > >This should be well known to devfs users. > >devfs sets at least some of the times before adjkerntz can run, and nothing >fixes them, so these times are wrong by the timezone difference.
This is not any different from any other filesystem. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message