[Bug 1201978] dracut assumes BIOS time is UTC closed without fixing again

Robert Nichols rnicholsNOSPAM at comcast.net
Fri May 1 14:25:43 UTC 2015


On 04/30/2015 06:37 PM, Adam Williamson wrote:
> I'd prefer objective analysis over anecdata. poettering's contention
> is :
>
> i) there is only a problem if you have time-based fsck enabled
> ii) this is not the default

In addition, it's only going to be a problem when fsck is run during
early boot, before the kernel's clock has been adjusted for having
been initially set to local time from the RTC.  And even then, it
depends on whether your time zone offset is positive or negative.

In the goode olde days, fsck was performed from rc.sysinit long
after the kernel's clock was set correctly, so the effect of RTC
in local time was just some bogus timestamps in the boot log.  Now,
with more tasks performed in early boot, the effect of a large
positive or negative shift in the kernel's clock can be more severe.

-- 
Bob Nichols     "NOSPAM" is really part of my email address.
                 Do NOT delete it.



More information about the devel mailing list