Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Carlos Santos <casantos@datacom.ind.br>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 0/2] Fix fsck issues regarding merged /sbin and /usr/sbin
Date: Mon,  3 Apr 2017 12:06:34 -0300	[thread overview]
Message-ID: <1491231996-2461-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.

In order to solve the problem we need to make two changes:

- Fix e2fsprogs to prevent removing/overriding the fsck 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: favor util-linux's fsck wrapper over e2fsprogs one
  systemd: select fsck wrapper from util-linux

 package/e2fsprogs/Config.in    |  4 ++++
 package/e2fsprogs/e2fsprogs.mk | 17 ++++++++++++-----
 package/systemd/Config.in      |  6 ++++++
 3 files changed, 22 insertions(+), 5 deletions(-)

-- 
2.7.4

             reply	other threads:[~2017-04-03 15:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-03 15:06 Carlos Santos [this message]
2017-04-03 15:06 ` [Buildroot] [PATCH v4 1/2] e2fsprogs: favor util-linux's fsck wrapper over e2fsprogs one Carlos Santos
2017-04-03 15:06 ` [Buildroot] [PATCH v4 2/2] systemd: select fsck wrapper from util-linux Carlos Santos
2017-04-24 19:22   ` Peter Korsgaard

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=1491231996-2461-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox