From: Detlef Vollmann <dv@vollmann.ch>
To: openembedded-devel@openembedded.org
Subject: Splitting an image into multiple partitions
Date: Wed, 08 Apr 2009 15:07:30 +0200 [thread overview]
Message-ID: <49DCA192.90905@vollmann.ch> (raw)
Hello,
splitting your systems into different partitions often makes sense.
So this means you have to create a number of different images,
each comprising of a specific part of the full filesystem.
Doing that for one specific project is actually pretty easy,
but then you loose all the flexibility of image.bbclass.
Adding an additional variable to image.bbclass and calling
bbimage with an '-r' argument is also not a big deal, but
this way you have to do all the work to put together the
rootfs several times.
With only two partitions, you could just build the separate
partition first (e.g. '/mnt1'), then delete that part from
IMAGE_ROOTFS, and then build the rootfs.
But this doesn't work for more than two partitions.
IMHO an optimum solution would be to add an '--exclude'
option to bbimage that you can give several times, then
image.bbclass could just go through a list of partitions
and create one after the other.
But maybe I just look into the wrong direction, and there's
a much easier way for doing what I try to do.
Any hints are appreciated.
Detlef
reply other threads:[~2009-04-08 13:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=49DCA192.90905@vollmann.ch \
--to=dv@vollmann.ch \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.org \
/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.