From: AAlex_ <earthquake.de@freenet.de>
To: buildroot@busybox.net
Subject: [Buildroot] makedev capabilities support - capablities lost after booting the image
Date: Mon, 16 Apr 2018 05:17:42 -0700 (MST) [thread overview]
Message-ID: <1523881062231-0.post@n4.nabble.com> (raw)
Hi,
setting the cappabilities of an executable via BR2_ROOT_FS_DEVICE_TABLE as
descripted in [9.5.1. Setting file permissions and ownership and adding
custom devices nodes] fails.
When capabilities specified to an file they are set in the disk image, means
if i mount the disk image file and check via getcap it get the excpected
capabilities.
But if the builroot system boots, the capablities are lost.
Is there another lib/flag? The buildroot system supports capabilities
because I set it via an startscript within buildroot system, but this is not
longer possible because I want to swtich to read only root_fs. This is the
reason I want to set the capablilities via device_table.
Regards,
Alex
--
Sent from: http://buildroot-busybox.2317881.n4.nabble.com/
next reply other threads:[~2018-04-16 12:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 12:17 AAlex_ [this message]
2018-04-16 12:31 ` [Buildroot] makedev capabilities support - capablities lost after booting the image Baruch Siach
2018-04-16 20:18 ` AAlex_
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=1523881062231-0.post@n4.nabble.com \
--to=earthquake.de@freenet.de \
--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.