From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Chances in skeleton don't appear in filesystem
Date: Tue, 4 Dec 2012 10:03:44 +0100 [thread overview]
Message-ID: <20121204100344.3167d0e9@skate> (raw)
In-Reply-To: <slrnkbqn5h.1p8.narkewoody@zuhnb712.local.com>
Dear Woody Wu,
On Tue, 4 Dec 2012 02:16:11 +0000 (UTC), Woody Wu wrote:
> After some intial builds, I come up with idea to make chances in the
> default filesystem contents. Then I change the config to use customized
> filesystem skeleton (fs/skeleton) and changed the
> fs/skeleton/network/interfaces with expection that change could appear
> in the generated target file system. After another run of make,
> however, I did not see my chances by untar the rootfs.tar.bz2.
The skeleton is copied to output/target during the first make, and is
not copied again during subsequent invocations of make. If you want to
see your filesystem skeleton changes to be taken into account, you have
to do a "make clean; make" cycle.
> Then I
> tried to remove the output/target directory, this time I even got
> another error, 'output/target/etc/hosts: no such file or directory'.
Removing the output/target directory does not make sense and cannot
work. Buildroot does not know that it has been removed and therefore
does not retrigger the installation of all packages.
> What's the correct method to modify the defualt filesystem? Thanks.
Do use a custom skeleton, use a custom post-build script to copy/modify
files in output/target. See
http://elinux.org/images/2/2a/Using-buildroot-real-project.pdf starting
slide 22, and particularly slides 24 and 25.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-12-04 9:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-04 2:16 [Buildroot] Chances in skeleton don't appear in filesystem Woody Wu
2012-12-04 4:44 ` Woody Wu
2012-12-04 9:03 ` Thomas Petazzoni [this message]
2012-12-04 23:29 ` Peter Korsgaard
2012-12-12 16:26 ` Woody Wu
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=20121204100344.3167d0e9@skate \
--to=thomas.petazzoni@free-electrons.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 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.