From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC] How to handle targets that need more than one file system to boot?
Date: Thu, 03 Jan 2013 11:30:02 +0100 [thread overview]
Message-ID: <87wqvuo8yd.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <201301030940.07495.yann.morin.1998@free.fr> (Yann E. MORIN's message of "Thu, 3 Jan 2013 09:40:07 +0100")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
Hi,
Yann> The reason for wanting to include such a feature in Buildroot is to
Yann> keep Buildroot ximple to use for the *end-user*, not necessarily for
Yann> the Buildroot developpers. A little bit of complexity in the Buildroot
Yann> Makefiles and script is OK if it makes for an smoother user experience.
Yann> And if you have those files in images/ :
Yann> - images/boot-vfat.img
Yann> - images/root-squahfs.img
Yann> - images/home-ext2.img
Yann> Then it is a matter of running (/dev/sdX is the sd-card):
Yann> - dd if=images/boot-vfat.img of=/dev/sdX1
Yann> - dd if=images/root-squashfs.img of=/dev/sdX2
Yann> - dd if=images/home-ext2.img of=/dev/sdX3
Except this doesn't take care of resizing the filesystems to span the
entire partition.
The linaro people afaik have a linaro-media-create tool to automate
something like this, perhaps we could use it?
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2013-01-03 10:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-24 0:00 [Buildroot] [RFC] How to handle targets that need more than one file system to boot? Yann E. MORIN
2012-12-25 3:52 ` Steve Calfee
2013-01-02 6:57 ` Arnout Vandecappelle
2013-01-02 23:56 ` Yann E. MORIN
2013-01-03 0:32 ` Steve Calfee
2013-01-03 8:31 ` Willy Lambert
2013-01-03 17:33 ` Yann E. MORIN
2013-01-03 17:54 ` Bjørn Forsman
2013-01-03 18:08 ` Yann E. MORIN
2013-01-03 8:40 ` Yann E. MORIN
2013-01-03 8:52 ` Jeremy Rosen
2013-01-03 8:53 ` Arnout Vandecappelle
2013-01-03 8:57 ` Thomas Petazzoni
2013-01-03 9:13 ` Yann E. MORIN
2013-01-03 10:30 ` Peter Korsgaard [this message]
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=87wqvuo8yd.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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