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.
14 листопада 2009 о 15:57 -0500 Theodore Tso написав(-ла): > There are a number of workarounds. One is to take the kernel patch > (or upgrading to 2.6.32, which will have the fix). Or you can fix > your system clock to tick GMT, as opposed to localtime, which is > fraught with all sorts of problems, especially around the transition > in and out of summer-time/daylight savings time. Or you add the > following stanza to /etc/e2fsck.conf: > > [options] > buggy_init_scripts = 1 > > One could just as easily argue that the real bug is having the > hardware CMOS time tick in localtime. Granted we should make the > system more robust against people who incorrectly set their system > clock to be bug-for-bug compatible with Microsoft, but in no way does > this justify increasing the severity to "grave". > > In fact we do have changes pending in e2fsprogs and in the kernel to > make things more robust against brain-damaged configurations. See > commit ba5131f6 in the e2fsprogs maint branch. Until these changes > find their way into Debian packages, my recommendation is to either > (a) fix your hardware clock to tick UTC time, or (b) apply the > buggy_init_scripts workaround to /etc/e2fsck.conf. > > - Ted
signature.asc
Description: Digital signature
