linux-kernel - Re: The ext3 way of journalling

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 10 Jan 2008 15:41:11 +0200
From:	Tuomo Valkonen <tuomov@....fi>
To:	Theodore Tso <tytso@....edu>, linux-kernel@...r.kernel.org
Subject: Re: The ext3 way of journalling

On 2008-01-10 08:16 -0500, Theodore Tso wrote:
> > It displays just the right time. On boot anyway. (Linux has had some
> > serious problems keeping the time after the switch from 2.6.7 to 2.6.14,
> > advanding even 15 minutes a day -- that ntpd doesn't seem to be able 
> > to keep up with -- requiring running adjtimexconfig every now and
> > then for new settings. But the cmos clock displays the right time.)
> 
> What do you mean by "on boot"?  Which boot message, precisely?  Is the
> time printed before or after e2fsck is run, and by which program?

The time is right as displayed by `date` after boot, i.e. after it has
been loaded from the CMOS clock that does keep the (local, IIRC) time
just allright. But then it often starts advancing very fast.

-- 
Tuomo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/