From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] How to organize build into multiple target filesystems?
Date: Mon, 6 Mar 2017 00:52:46 +0100 [thread overview]
Message-ID: <fa8d21ca-56d4-9561-bc25-333c238abfb5@mind.be> (raw)
In-Reply-To: <CABKRrCWcWO3MNBnFK9fAoaYoGQBNn2eN=ZvZYovHvV1jwYQbSw@mail.gmail.com>
Hi Dave,
A bit late to answer this, but perhaps still relevant.
On 21-02-17 20:08, David Wuertele wrote:
> I would like my target to have a small initramfs, and a large-ish /usr
> filesystem mounted at runtime. The initramfs will be populated with some of my
> packages, the usr fs will be populated with the rest. I don't want the
> initramfs to contain anything under usr except for the /usr mountpoint
> directory.
>
> In general, I'm looking for a way to divert my package outputs into an
> arbitrary number of filesystems, which I then package in various ways,
> including but not limited to bundling into a kernel initramfs.
>
> Is there a way to specify such an organization in buildroot?
Not directly. The Buildroot Way is to keep things simple, preferably without
blocking real use cases. For your use case, you need specific treatment in a
fakeroot script.
Buildroot will still build a monolithic filesystem, and your fakeroot script
can extract parts that need special treatment. For example, you can make a
tarball of $TARGET_DIR/usr, then remove the /usr tree, or remove the part that
you don't need. You can also use $BUILD_DIR/packages-file-list.txt to find out
which file comes from which package, to do this on a per-package basis.
You will also need to add the necessary scripts (or systemd units) in a rootfs
overlay to stitch things back together.
I'm adding Thomas DS in Cc, he described a somewhat similar setup in the last
BR developer meeting.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2017-03-05 23:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 19:08 [Buildroot] How to organize build into multiple target filesystems? David Wuertele
2017-03-05 23:52 ` Arnout Vandecappelle [this message]
2017-03-21 20:34 ` Thomas De Schampheleire
2017-03-22 7:45 ` Thomas De Schampheleire
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=fa8d21ca-56d4-9561-bc25-333c238abfb5@mind.be \
--to=arnout@mind.be \
--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.