On Fri, Feb 8, 2013 at 12:05 PM, Colin Guthrie <gm...@colin.guthr.ie> wrote: > 'Twas brillig, and Kok, Auke-jan H at 08/02/13 08:04 did gyre and gimble: >> On Thu, Feb 7, 2013 at 3:38 PM, Lennart Poettering >> <lenn...@poettering.net> wrote: >>> On Thu, 07.02.13 16:57, Bryan Duff (bd...@ecessa.com) wrote: >>> >>>> Would it be possible to add this as some kind of option to systemd-fsck? >>>> >>>> In my case there was a situation where ext3 would not mount because >>>> of a timestamp issue that would not be fixed with "-a". >>> >>> Every sane distro patches the timestamp check nonsense out of >>> e2fsck. Assuming the RTC was always correct is just so misguided, it >>> hurts... >> >> ACK, sadly, I've applied this patch too several times... > > By "patches" here I think all we did was ship a /etc/e2fsck.conf with: > > [options] > # This will prevent e2fsck from stopping boot just because the clock is > wrong > broken_system_clock = 1 > > in it. I don't think there is much else needed (please correct me if I'm > wrong!).
Right. Don't forget to put it into the initramfs, if needed. The whole thing is still a pointless and broken feature. It's the wrong default, if the feature is ever useful for anybody. There are systems without any clock, and a file system checker to make assumptions about the system time, makes zero sense; setups without a clock are just fine. Well, there will be btrfs ... :) Kay _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
