From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] fs: ensure hard links in TARGET_DIR are correctly copied for filesystem input
Date: Sun, 27 May 2018 23:46:49 +0200 [thread overview]
Message-ID: <877enon54m.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180527204857.6081-1-peter@korsgaard.com> (Peter Korsgaard's message of "Sun, 27 May 2018 22:48:57 +0200")
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
> Fixes #11046
> Commit bb2a57a17a7 (fs: run packages' filesystem hooks in a copy of target/)
> changed the file system logic to run file system hooks from packages on a
> copy of TARGET_DIR, and finally use this copy as input for the file system
> generation.
> This copy was done with rsync, which by default does not preserve hard
> links, leading to an expansion of the file system images when hard links are
> present.
> Fix it by passing the -H option to rsync (preserve hard links).
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
> ---
> Alternatively we can use 'cp -a' instead of rsync.
Committed, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2018-05-27 21:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-27 20:48 [Buildroot] [PATCH] fs: ensure hard links in TARGET_DIR are correctly copied for filesystem input Peter Korsgaard
2018-05-27 21:39 ` Yann E. MORIN
2018-05-27 21:46 ` Peter Korsgaard [this message]
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=877enon54m.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--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.