Theodore Tso writes ("Re: Bug#441093: fix last check time in future"):
> I'm not going to apply this patch, because it could be the clock is
> totally bogus, and in that case, you *do* want to do an fsck, because
> it could have been a very, very long time since a check had been done.I did consider putting a limit on the amount into the future that was allowed (say, 48h) but in practice if the clock is that wrong on one boot then when you fix it it'll sort itself out. > My plan for fixing this given all of the whinging and "it's impossible > to fix this" is that distros who believe this can set in /etc/e2fsck.conf: Right. Fair enough. I would be happy explain what the problems are with getting the time right but I'm sure you've had plenty of representations along those lines already. If you're interested, let me know. Ian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
