On Sun, Nov 15, 2009 at 10:34:33PM +0100, Eugeniy Meshcheryakov wrote:
> Hello,
>
> Thanks for reply. This option will probably fix problem with systems
> with clock set to local timezone, but not for systems like FreeRunner
> where clock content is lost when battery is removed. It will be good to
> have option that disables mount time in the future check entirely.
Note that the file system isn't the only place that might assume that
time is correct. For example, the UUID generation algorithm derives
its uniqueness guarantees from the fact that time is correctly set.
If you don't have an accurate clock, you may have all sorts of strange
behavior as a result.
As far as the FreeRunner is concerned, it currently takes me under 8
seconds to check a 70gig SSD drive. If you put 8GB SD card into the
FreeRunner smartphone, the first check after a failed battery should
take at most a second. Hardly worth people going into hysterics and
calling this a "grave" bug.
If you really want to disable the future check, you can do this:
[problems]
0x000031 = {
preen_ok = true
}
0x000032 = {
preen_ok = true
}
I consider this a botch to work around broken hardware, though...
- Ted
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
