From: Petr Vorel <petr.vorel@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] iputils: set the permissions with IPUTILS_PERMISSIONS
Date: Tue, 18 Jun 2019 22:52:12 +0200 [thread overview]
Message-ID: <20190618205211.GC20410@x230> (raw)
In-Reply-To: <87wohjxdsk.fsf@dell.be.48ers.dk>
Hi Peter,
> >> >> Is there an easy way to detect
> >> >> iso9660 usage?
> >> > BR2_TARGET_ROOTFS_ISO9660 of course. Well, that one is special actually because
> >> > in case of BR2_TARGET_ROOTFS_INITRAMFS or BR2_TARGET_ROOTFS_ISO9660_INITRD, the
> >> > rootfs is not actually stored in the iso9660.
> >> > But I don't know which other filesystems lack support for xattrs.
> >> axfs, cramfs, romfs and yaffs2 as well afaik.
> > Thanks a lot.
> > I guess BR2_TARGET_ROOTFS_TAR (and other tarballs supported)
> > supports xattrs (--xattrs-include='*' in fs/tar/tar.mk).
> > It'd be nice if buildroot has BR2_TARGET_ROOTFS_HAS_XATTRS.
> The problem is that you can enable several rootfs formats at the same
> time (E.G. tar and cramfs), so we would need to only use xattrs if no
> file system without xattrs support is enabled.
> And things would break if you do a build with E.G. only tar rootfs
> support and then afterwards enable cramfs without doing a clean
> rebuild - Yes, I know you are not supposed to do that, but it does
> happen.
Thanks for detailed info. I guess in that case is setuid really the only option.
Kind regards,
Petr
next prev parent reply other threads:[~2019-06-18 20:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-09 23:07 [Buildroot] [PATCH 1/1] iputils: set the permissions with IPUTILS_PERMISSIONS Petr Vorel
2019-06-10 13:45 ` Arnout Vandecappelle
2019-06-10 20:06 ` Petr Vorel
2019-06-10 21:26 ` Arnout Vandecappelle
2019-06-13 19:37 ` Peter Korsgaard
2019-06-14 16:24 ` Petr Vorel
2019-06-18 12:45 ` Peter Korsgaard
2019-06-18 20:52 ` Petr Vorel [this message]
2019-06-18 21:31 ` Arnout Vandecappelle
2019-06-19 5:01 ` Petr Vorel
2019-06-19 6:50 ` Arnout Vandecappelle
2019-06-19 6:52 ` Petr Vorel
2019-06-19 7:11 ` 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=20190618205211.GC20410@x230 \
--to=petr.vorel@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox