From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Possible conflict with systemd and e2fsprogs?
Date: Sat, 27 Apr 2019 19:56:17 +0200 [thread overview]
Message-ID: <7bb7a201-cdd2-7e66-deee-6175a264366c@mind.be> (raw)
In-Reply-To: <4dcaadcb-0ef8-887e-6681-1f326194315c@digineo.de>
On 25/04/2019 20:15, Dominik Menke wrote:
> Greetings,
>
> I've run into trouble with the following configuration on Buildroot
> 2019.02.1-100-g88eff22a9e (current 2019.02.x branch):
>
> ??? (
> ????? echo BR2_INIT_SYSTEMD=y
> ????? echo BR2_PACKAGE_E2FSPROGS=y
> ??? ) | cat configs/raspberrypi3_defconfig - > configs/myrpi_defconfig
> ??? make myrpi_defconfig
[snip]
> Looking at /usr/lib/systemd/systemd-fsck (which is executed by
> systemd-fsck-root.service), it calls to /sbin/fsck only if /sbin/fsck.$type
> exists [3]. My guess is that it then fails to proceed because e2fsprog's fsck
> behaves differently then fsck (of package util linux).
It would be good to find out what exactly is going wrong.
package/systemd/Config.in does select BR2_PACKAGE_UTIL_LINUX_FSCK precisely for
this reason...
I'm adding Carlos (who added that) in Cc, maybe he has something to say about it.
If it now needs the fsck from e2fsprogs, then it is getting a little tricky to
do the right thing. We'd have to revert the dependency between e2fsprogs fsck
and util-linux fsck.
However, I seem to recall that e2fsprogs fsck was considered deprecated.
Regards,
Arnout
next prev parent reply other threads:[~2019-04-27 17:56 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 [this message]
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
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=7bb7a201-cdd2-7e66-deee-6175a264366c@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