From: Carlos Santos <casantos@datacom.ind.br>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v5 0/2] e2fsprogs: fix issues when BR2_ROOTFS_MERGED_USR=y
Date: Mon, 10 Apr 2017 00:23:14 -0300 [thread overview]
Message-ID: <1491794596-8454-1-git-send-email-casantos@datacom.ind.br> (raw)
Since e2fsprogs depends on util-linux, it's build after it. It means
that if you want the fsck wrapper from util-linux (which is better
maintained and you are sure that it's compatible with systemd) and you
want e2fsck, it won't work. Because of the merge of /usr/bin and /bin,
we end up deleting the fsck from util-linux.
The root cause of this problem is the cluncky attempt to coexist with
busybox and util-linux. In order to solve the problem we need to make
two changes:
- Refactor e2fsprogs, making it override any utility coming from busybox
and favoring the fsck wrapper from util-linux.
- Make systemd select util-linux/fsck to prevent ending up with the fsck
from busybox, which is not compatible with systemd.
Carlos Santos (2):
e2fsprogs: refactor to fix conflicts with busybox and util-linux
systemd: select util-linux/fsck and e2fsprogs/e2fsck
package/e2fsprogs/Config.in | 84 +++++++---------------
package/e2fsprogs/Config.in.host | 1 +
package/e2fsprogs/e2fsprogs.mk | 149 +++++++++++----------------------------
package/systemd/Config.in | 3 +
4 files changed, 71 insertions(+), 166 deletions(-)
--
2.7.4
next reply other threads:[~2017-04-10 3:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-10 3:23 Carlos Santos [this message]
2017-04-10 3:23 ` [Buildroot] [PATCH v5 1/2] e2fsprogs: refactor to fix conflicts with busybox and util-linux Carlos Santos
2017-04-10 3:23 ` [Buildroot] [PATCH v5 2/2] systemd: select util-linux/fsck and e2fsprogs/e2fsck Carlos Santos
2017-04-10 11:02 ` Maxime Hadjinlian
2017-04-10 11:13 ` Arnout Vandecappelle
2017-04-10 11:30 ` Maxime Hadjinlian
2017-04-10 11:44 ` Arnout Vandecappelle
2017-04-10 12:09 ` Carlos Santos
2017-04-10 12:22 ` Maxime Hadjinlian
2017-04-10 13:23 ` Arnout Vandecappelle
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=1491794596-8454-1-git-send-email-casantos@datacom.ind.br \
--to=casantos@datacom.ind.br \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.