Indeed, jaunty had a switch to fsck to "automatically repair" that issue
- upstream put it there claiming we had buggy init scripts.
We took it out because we're damned sure our scripts are right (the fact
the "now" time is always correct when you hit the fsck shell confirms
that), and wanted to see what other bugs were underneath.
Enough duplicates of this issue now appear, which after debugging turn
out to be local configuration issues, hardware clock reliability issues,
virtualisation issues, and simple human error issues, that I'm convinced
that "automatic repair" is the right way forward.
I'll be patching e2fsck today to fix that issue with -a again
** Also affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- fsck says last write time in future
+ UTC should be "no" when installing under VirtualBox
--
UTC should be "no" when installing under VirtualBox
https://bugs.launchpad.net/bugs/427822
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
