Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: David Bonnin <dboml@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] post-buil script in chrooted
Date: Tue, 16 Oct 2012 00:03:23 +0200	[thread overview]
Message-ID: <507C882B.5080609@free.fr> (raw)
In-Reply-To: <507866D6.8020608@mind.be>

Hello,

yes, sorry , i mean ,  i was looking for a post-build script for my 
board in a fakeroot environnement.
customize package is deprecated.

in board/me/Myproject/rootfs-adds/root/

i want to cp files of root user.

So i need to use custom skeletonfs or use customize package.

Is there a better way to do it?

thanks.

customize package
Le 12/10/2012 20:52, Arnout Vandecappelle a ?crit :
> On 12/10/12 10:41, Thomas De Schampheleire wrote:
>> On Fri, Oct 12, 2012 at 9:30 AM, Thomas Petazzoni
>> <thomas.petazzoni@free-electrons.com>  wrote:
>>> >  Dear David Bonnin,
>>> >
>>> >  On Fri, 12 Oct 2012 07:18:24 +0200, David Bonnin wrote:
>>> >
>>>> >>  Few ask in finalise target:
>>>> >>  1- to do root task, i can only use permission: target in each
>>>> >>  packages..........
>>> >
>>> >  Not sure I understand this part.
>>> >
>>>> >>  CAN i use a "root script" in chrooted mode?
>>>> >>  ROOTFS_POST_BUILD_SCRIPT is not executed chrooted in the target.
>>> >
>>> >  No because it doesn't make sense. Buildroot is used in many cases 
>>> for
>>> >  cross-compilation, so the development machine is x86 or x86_64 
>>> and the
>>> >  target filesystem contain ARM, PowerPC or MIPS binaries. So 
>>> chrooting
>>> >  into it is not possible (unless we use Qemu or something like 
>>> that, but
>>> >  it's not the idea of Buildroot, we want to do cross-compilation).
>> Maybe you can explain why you think chroot would be necessary. What
>> are you trying to accomplish?
>> If you need to add device nodes for example, there are other ways to
>> do it without needing to be root.
>
>  I think he means fakeroot, not chroot...
>
>  I can think of some things for which you may want to execute a fakeroot
> script:
>
> - to set xattrs or acls (though I'm not sure if libfakeroot supports 
> them);
> - to run some other 'filesystem generation' program, e.g. rsync or nfsd
> (we would create a new rootfs type for that, but Joe R. User may have a
> hard time doing that).
>
>
>  But most likely, what David needs is covered by BR2_ROOTFS_DEVICE_TABLE.
>
>
>  Regards,
>  Arnout

  reply	other threads:[~2012-10-15 22:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-12  5:18 [Buildroot] post-buil script in chrooted David Bonnin
2012-10-12  7:30 ` Thomas Petazzoni
2012-10-12  8:41   ` Thomas De Schampheleire
2012-10-12 18:52     ` Arnout Vandecappelle
2012-10-15 22:03       ` David Bonnin [this message]
2012-10-17 20:32         ` Arnout Vandecappelle
2012-10-26 20:56           ` David Bonnin
2012-10-26 23:05             ` Arnout Vandecappelle

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=507C882B.5080609@free.fr \
    --to=dboml@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