Well, the problem is fundamentally more about the initscripts and util- linux than it is about e2fsprogs. The message printed by e2fsprogs will change, so that it says the time is in the future, as opposed to 49710 days. But the root cause of the bug really is the fact that the system clock is not set correctly at the time the root filesystem is checked. Even with the future version of e2fsprogs, if the time is incorrect, a filesystem check will be forced when it doesn't need to be, which is what users really complain about. Simply changing the message isn't going to keep users from getting upset (and they deserve to be).
I had thought the bug was fixed since util-linux moved the hwclock.sh to rcS.d/S8hwclock.sh in version 2.12r-13, and Feisty is using 2.12r- 17ubuntu, but I see that upon closer inspection it looks like Feisty still has hwclock.sh started at S50 (and Debian still has it as S11 instead of S8, argh; so bug #342887 was inappropriately closed in Debian, sigh). So I believe the correct answer at this point is that an Ubuntu task against util-linux needs to be kept open against the Ubuntu util-linux package, since that is where the correct patch should be applied. Does that sound right to you? -- fsck should check against a timestamp "49710 days" old https://bugs.launchpad.net/bugs/43239 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
