At a guess, your Jaunty and Karmic installations disagree about whether the hardware clock should be to tick localtime or UTC time, and one of the things the shutdown scripts do is to set the hardware clock from the system clock. This causes the time at boot up to be incorrect until NTP has a chance to correct things.
This isn't an e2fsprogs bugs, but rather a system configuration error. -- fsck halts bootup when checked file has timestamp in the future from other Ubuntu installation https://bugs.launchpad.net/bugs/422869 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
