From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC PATCH v2 1/2] makedevs: only warn on xattr when not enabled
Date: Tue, 30 Jul 2019 19:46:51 +0200 [thread overview]
Message-ID: <20190730174651.GG3194@scaer> (raw)
In-Reply-To: <20190729230644.2423-1-petr.vorel@gmail.com>
Petr, All,
On 2019-07-30 01:06 +0200, Petr Vorel spake thusly:
> Previously makedevs failed on adding xattr when
> BR2_ROOTFS_DEVICE_TABLE_SUPPORTS_EXTENDED_ATTRIBUTES was not enabled.
> Now only warn. Therefore check for this configuration would be required
> in each use. But no package is using it so far (it's used only in tests).
>
> Signed-off-by: Petr Vorel <petr.vorel@gmail.com>
> ---
> Hi,
>
> this supersede this patch:
> https://patchwork.ozlabs.org/patch/1138055/
>
> Unfortunately I wasn't able to test it as
> buildroot/output/build/buildroot-fs/tar/fakeroot is not working for me.
> Can anyone test it?
>
> Kind regards,
> Petr
>
> package/makedevs/makedevs.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/package/makedevs/makedevs.c b/package/makedevs/makedevs.c
> index c57b964f5c..ab35b8e70d 100644
> --- a/package/makedevs/makedevs.c
> +++ b/package/makedevs/makedevs.c
> @@ -518,8 +518,9 @@ int main(int argc, char **argv)
> if (bb_set_xattr(full_name, xattr) < 0)
> bb_error_msg_and_die("can't set cap %s on file %s\n", xattr, full_name);
> #else
> - bb_error_msg_and_die("line %d not supported: '%s'\nDid you forget to enable "
> - "BR2_ROOTFS_DEVICE_TABLE_SUPPORTS_EXTENDED_ATTRIBUTES?\n",
> + bb_error_msg("line %d not supported: '%s'\nEnable "
> + "BR2_ROOTFS_DEVICE_TABLE_SUPPORTS_EXTENDED_ATTRIBUTES"
> + "to get xattr support\n",
It would be nice if the message was displayed only the first time an
xattr line is encountered, something like:
if (!xattr_warned) {
bb_error_msg(...);
xattr_warned = 1;
}
Regards,
Yann E. MORIN.
> linenum, line);
> #endif /* EXTENDED_ATTRIBUTES */
> continue;
> --
> 2.22.0
>
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2019-07-30 17:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-29 23:06 [Buildroot] [RFC PATCH v2 1/2] makedevs: only warn on xattr when not enabled Petr Vorel
2019-07-29 23:06 ` [Buildroot] [RFC PATCH v2 2/2] iputils: add capability for clockdiff, ping, traceroute6 Petr Vorel
2019-07-30 17:46 ` Yann E. MORIN [this message]
2019-07-30 20:00 ` [Buildroot] [RFC PATCH v2 1/2] makedevs: only warn on xattr when not enabled Petr Vorel
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=20190730174651.GG3194@scaer \
--to=yann.morin.1998@free.fr \
--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