From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Advice on buildroot implementation
Date: Wed, 20 Feb 2013 00:18:50 +0100 [thread overview]
Message-ID: <5124085A.1080903@mind.be> (raw)
In-Reply-To: <718DFA7882181D45B8BD18F31C46D55427A6A8E3@MBX204.domain.local>
On 20/02/13 00:03, Gregory Perry wrote:
> Hello again,
>
> Does anyone have some advice on using buildroot to create a LiveCD filesystem?
>
> Here are the requirements:
>
> 1) Universal boot support on any x86 hardware platform;
> 2) Read only (UnionFS or OverlayFS); and
> 2) NFS root capabilities after kernel/initrd launch (if the ISO is PXE-boostrapped)
On x86, I find the easiest approach to use a cpio initramfs, with a
syslinux boot loader. But if universal boot is required, it means you
have to stuff all the modules bloat in the cpio image...
For basic boot you don't need unionfs. The NFS root you can have by
combining the cpio initramfs with a unionfs overlay (assuming the
initramfs contains all the modules and firmware). I posted a script
recently [1] to mount a unionfs-root early in init. Don't forget to
select the unionfs-fuse package.
Regards,
Arnout
[1] http://lists.busybox.net/pipermail/buildroot/2013-January/066146.html
> The problems I am seeing with this approach so far (at least from the NFS
> root perspective) is that things like /lib/firmware are not accessible during the
> boot process which hangs the boot process.
>
> Has anyone successfully created a buildroot install that can be used over a
> read only NFS mount? How did you get around issues like eth0 firmware not
> being accessible during the initial boot?
>
> Thanks in advance
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
>
--
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: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2013-02-19 23:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-19 23:03 [Buildroot] Advice on buildroot implementation Gregory Perry
2013-02-19 23:18 ` Arnout Vandecappelle [this message]
2013-02-20 1:24 ` Gregory Perry
2013-02-20 11:08 ` Stefan Fröberg
2013-02-20 17:38 ` Arnout Vandecappelle
2013-02-21 10:38 ` Stefan Fröberg
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=5124085A.1080903@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox