Date: Thu, 6 Feb 2003 13:31:45 +0300 From: "Andrey A. Chernov" <ache@nagual.pp.ru> To: phk@freebsd.org Cc: Bruce Evans <bde@zeta.org.au>, current@freebsd.org Subject: Re: Wrong date for DEVFS entries Message-ID: <20030206103144.GB12538@nagual.pp.ru> In-Reply-To: <1091.1044527256@critter.freebsd.dk> References: <20030206193118.T72545-100000@gamplex.bde.org> <1091.1044527256@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Feb 06, 2003 at 11:27:36 +0100, phk@freebsd.org wrote: > In message <20030206193118.T72545-100000@gamplex.bde.org>, Bruce Evans writes: > >On Thu, 6 Feb 2003, Andrey A. Chernov wrote: > > > >> On Wed, Feb 05, 2003 at 23:44:08 +0100, phk@freebsd.org 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. No, it IS different - no real filesystems mounted at this point yet, so no real timestamps damaged. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030206103144.GB12538>