On Thu, Sep 24, 2009 at 06:15:43PM -0400, Theodore Tso wrote: > On Thu, Sep 24, 2009 at 12:25:00PM +0200, Marc Haber wrote: > > I think that this timestamp check is too picky and should be removed > > completely or relaxed in a way that it does only return a non-zero > > exit code if the difference is more than could be explained by a > > timezone issue. > > There is an easy fix for this, which used to be installed by default > on Ubuntu (but not on Debian systems, where this hasn't been a > problem). This was an automatic installation of the following in > /etc/e2fsck.conf: > > [options] > buggy_init_scripts = 1
I have set this now after the issue happening to me after a _CLEAN_ shutdown of the system. > But if you're really annoyed and you think it's "too picky" to make > sure the time zones are set correctly in early boot, It is OK to expect time zones to be correct in early boot of the productive system, but it is, IMO, too picky to expect this from a rescue system. Please consider renaming the option to "relax_superblock_time_check" since we do not have a case of buggy init scripts here. And please consider that you might not be seeing the issue in its full impact since your timestamp is always in the past. European's time stamps are always in the future, so we are much more affected by the issue since _our_ systems don't cleanly boot. Greetings Marc -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 621 72739835 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
