From: "Sørensen, Stefan" <Stefan.Sorensen@spectralink.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] fs: add custom fakeroot script support
Date: Wed, 25 Feb 2015 12:02:41 +0000 [thread overview]
Message-ID: <1424865760.2629.14.camel@e37108.spectralink.com> (raw)
In-Reply-To: <20150224213941.GB4783@free.fr>
On Tue, 2015-02-24 at 22:39 +0100, Yann E. MORIN wrote:
> > The scripts can for example be used to invoke a tool that operates on
> > file ownerships,
>
> For file ownership, we already have BR2_ROOTFS_DEVICE_TABLE: "Path to
> the permission tables". The naming of the option may be a bit
> misleading, indeed, but that's historical...
As you mention yourself, bulk ownership changes are problematic with
device tables. Generating the device table in the post-build script
doesn't seem very elegant to me.
> > or any other custom action that requires
> > root privileges.
>
> What would be those kind of "custom actions" that are not covered by the
> above?
An example could be changes to files/device nodes that are created
earlier in the script. We use it to remove /dev/console created
by /fs/cpio.mk (our image format doesn't support device nodes).
Creating a manifest file of the whole filesystem, including stuff added
by the fakeroot script, would also need to be done just before image
creation (although here there is no need for being root).
> > +config BR2_ROOTFS_FAKEROOT_SCRIPT
> > + string "Custom scripts to run as fake root"
>
> I'm not very happy with talking about 'fake root' (which is really
> 'fakeroot'). I'd prefer we avoid mentionning fakeroot, which is
> internal implementation details.
I will rewrite it to not mention fakeroot.
> Note also that those scripts would be run once for each filesystem type
> the user has enabled; if tar, squashfs, cramfs and ext2/3/4 are enabled,
> the scripts would be run four times. Thus, those scripts must be
> idempotent (like for the post-build scripts, mind you).
I will add a comment to the help text.
Stefan
next prev parent reply other threads:[~2015-02-25 12:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-24 15:47 [Buildroot] [PATCH 1/2] fs: Bail out on errors in fakeroot script Stefan Sørensen
2015-02-24 15:47 ` [Buildroot] [PATCH 2/2] fs: add custom fakeroot script support Stefan Sørensen
2015-02-24 21:39 ` Yann E. MORIN
2015-02-25 12:02 ` Sørensen, Stefan [this message]
2015-06-30 13:31 ` Thomas Petazzoni
2015-02-24 18:27 ` [Buildroot] [PATCH 1/2] fs: Bail out on errors in fakeroot script Yann E. MORIN
2015-03-08 21:23 ` Thomas Petazzoni
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=1424865760.2629.14.camel@e37108.spectralink.com \
--to=stefan.sorensen@spectralink.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