From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Possible conflict with systemd and e2fsprogs?
Date: Mon, 29 Apr 2019 22:37:30 +0200 [thread overview]
Message-ID: <6824ef05-10eb-d45a-4dd7-0fc75173473e@mind.be> (raw)
In-Reply-To: <df9e7287-f9b0-4381-6a04-3424ee752065@digineo.de>
On 29/04/2019 18:18, Dominik Menke wrote:
> [??? 4.547439] systemd-fsck[94]: /dev/mmcblk0p2: Superblock last write time (Mon
> Apr 29 17:37:11 2019,
> [??? 4.551637] systemd-fsck[94]:???? now = Thu Feb 14 11:11:59 2019) is in the
> future.
My systemd-fu is not great, but it looks weird that now = somewhere in 2019 if
you have no RTC. I believe fsck has code to ignore the time-in-future check if
now ~ 1970.
Regards,
Arnout
next prev parent reply other threads:[~2019-04-29 20:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-25 18:15 [Buildroot] Possible conflict with systemd and e2fsprogs? Dominik Menke
2019-04-27 17:56 ` Arnout Vandecappelle
2019-04-27 21:20 ` Dominik Menke
2019-04-27 21:47 ` Arnout Vandecappelle
2019-04-29 9:01 ` Dominik Menke
2019-04-29 16:18 ` Dominik Menke
2019-04-29 20:37 ` Arnout Vandecappelle [this message]
2019-04-30 10:23 ` Dominik Menke
2019-04-27 18:08 ` Yann E. MORIN
2019-04-27 21:02 ` Dominik Menke
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6824ef05-10eb-d45a-4dd7-0fc75173473e@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox