On Sat, 2009-10-10 at 20:19 +0000, Rob Speer wrote:
> Scott, that's a good explanation for how I can fix the situation in my
> case.
>
> Still, I don't think it's desirable to bail out to a root prompt just
> because the hardware clock is wrong, no matter how that came to be.
>
I agree.
Scott
--
Scott James Remnant
sc...@ubuntu.com
** Package changed: sysvinit (Ubuntu) => e2fsprogs (Ubuntu)
** Changed in: e2fsprogs (Ubuntu)
Status: New => Triaged
** Changed in: e2fsprogs (Ubuntu)
Importance: Undecided => High
** Changed in: e2fsprogs (Ubuntu)
Assignee: (unassigned) => Scott James Remnant (scott)
** Also affects: e2fsprogs (Ubuntu Karmic)
Importance: High
Assignee: Scott James Remnant (scott)
Status: Triaged
** Also affects: ubiquity (Ubuntu Karmic)
Importance: Undecided
Status: New
** Changed in: e2fsprogs (Ubuntu Karmic)
Milestone: None => ubuntu-9.10
--
superblock last write time is in the future
https://bugs.launchpad.net/bugs/268808
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
