In Gutsy, hwclock is started at S11, which in Ubuntu is after S10udev
and before S20checkroot.sh, so this should be fine now. Please reopen if
you can reproduce with Gutsy.
WRT to the question of fsck'ing if the timestamp is in the future: Then
you know the clock is wrong, and you can not trust it, and you should
fsck just to be sure.
** Changed in: util-linux (Ubuntu)
Status: Confirmed => Fix Released
--
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
