Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] iputils: set the permissions with IPUTILS_PERMISSIONS
Date: Thu, 13 Jun 2019 21:37:44 +0200	[thread overview]
Message-ID: <87muilgttj.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <7191f609-e5d8-7bd6-77ca-83296f96d0f1@mind.be> (Arnout Vandecappelle's message of "Mon, 10 Jun 2019 23:26:37 +0200")

>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:

 > On 10/06/2019 22:06, Petr Vorel wrote:
 >> Hi Arnout,
 >> 
 >>> Applied to master, thanks. I updated the commit message a little.
 >> Thanks! You've been faster, I might try to think about setcap (xattr) use if
 >> USE_CAP=true, and setuid if USE_CAP=false.

 >  Great!

 >> 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.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2019-06-13 19:37 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 [this message]
2019-06-14 16:24         ` Petr Vorel
2019-06-18 12:45           ` Peter Korsgaard
2019-06-18 20:52             ` Petr Vorel
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=87muilgttj.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox