Having chatted to ogra, we think that broken_system_clock and that
config snippet are both working fine.
The problem is that this results in a "fix" to the root filesystem, and
that in turn results in the requirement that we reboot (the mounted root
fs has changed!)
And rebooting clears the hardware clock again, so we do it all over
again in a loop.
There isn't a fix for this :-(
** Changed in: util-linux (Ubuntu Lucid)
Assignee: Scott James Remnant (scott) => (unassigned)
** Changed in: util-linux (Ubuntu Lucid)
Milestone: ubuntu-10.04 => None
** Changed in: util-linux (Ubuntu Lucid)
Status: Confirmed => Triaged
** Summary changed:
- there is no way to tell fsck to ignore broken clocks on embedded systems
+ Ignoring a broken clock results in infinite reboots; not ignoring results in
fsck failure; no solution to this problem
--
Ignoring a broken clock results in infinite reboots; not ignoring results in
fsck failure; no solution to this problem
https://bugs.launchpad.net/bugs/563618
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
