On Mon, Oct 12, 2009 at 9:38 AM, Luke <[email protected]> wrote:
> so this fix solved that problem as well. This indicates the bug is NOT
> in mountall but somewhere else, as the clock should not be getting moved
> after boot to a wrong time anyway.
Read the whole thread, please. There is more than one bug.
Of course, there is a bug in mountall (or any program calling it),
because it cycles. That's fundamentally wrong; graceful degradation
prescribes that it ends at a rescue shell; not at infinite cycling.
You are correct, though, with your notion that it is yet another bug
that the clock gets moved after boot.
Uwe
--
UNEXPECTED INCONSISTENCY: fails to boot ("last mount time is in the future")
https://bugs.launchpad.net/bugs/432070
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
