[OE-core] [PATCH v1] systemd: Avoid fsck because time is out of sync on first boot.

[Kristian Amlie]

By default, systemd uses its build time as the epoch. When systemd is
launched on a system without a real time clock, this time will be
detected as in the future and an fsck will be done.  Setting this to 0
results in an epoch of January 1, 1970 which is detected as an invalid
time and the fsck will be skipped.

Signed-off-by: Kristian Amlie <kristian.amlie at northern.tech>
---
 meta/recipes-core/systemd/systemd_234.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-core/systemd/systemd_234.bb b/meta/recipes-core/systemd/systemd_234.bb
index 6b8745b..86c04fe 100644
--- a/meta/recipes-core/systemd/systemd_234.bb
+++ b/meta/recipes-core/systemd/systemd_234.bb
@@ -170,6 +170,7 @@ EXTRA_OECONF = " --with-rootprefix=${rootprefix} \
                  --without-python \
                  --with-sysvrcnd-path=${sysconfdir} \
                  --with-firmware-path=${nonarch_base_libdir}/firmware \
+                 --with-time-epoch=0 \
                "
 # per the systemd README, define VALGRIND=1 to run under valgrind
 CFLAGS .= "${@bb.utils.contains('PACKAGECONFIG', 'valgrind', ' -DVALGRIND=1', '', d)}"
-- 
2.7.4