From: Enrico Joerns <ejo@pengutronix.de>
To: Kristian Amlie <kristian.amlie@mender.io>,
Patrick Ohly <patrick.ohly@intel.com>,
Eduard Bartosh <eduard.bartosh@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: Contents of non-rootfs partitions
Date: Wed, 23 Nov 2016 09:40:00 +0100 [thread overview]
Message-ID: <776827b7-ca3e-e319-c2f0-b8b15bef4fb2@pengutronix.de> (raw)
In-Reply-To: <6913e4bf-96dc-eefa-d214-9df5cde181b8@mender.io>
On 11/22/2016 12:54 PM, Kristian Amlie wrote:
> On 22/11/16 12:10, Patrick Ohly wrote:
>>> ...
>>
>> All of these introduce some special mechanism. Let me propose something
>> that might integrate better with the existing tooling:
>>
>> The "rootfs" directory gets redefined as representing the entire virtual
>> file system. When creating a disk image, it gets split up into different
>> partitions based on the image configuration.
>>
>> For example, the /home or /data directories in the rootfs could hold the
>> content that in some image configurations goes into separate partitions.
>>
>> The advantage of this approach is that the tooling for staging content
>> for image creation does not need to be changed. The same staged content
>> then can be used to create different images, potentially even using
>> different partition layouts.
>
> That's a very good idea. I think it beats all of my suggestions!
I totally agree with this solution, because it is the same approach we
are already using for several years.
Instead of wic we are using the genimage tool
(http://public.pengutronix.de/software/genimage/) together with a Yocto
class for easing image creation, but its pretty much the same concerning
its base purpose.
We called the option to split up 'mountpoint' while assuming that the
splitted partition will be mounted to the same location in the file
system it was taken from.
An example configuration would look like this (stripped down to the
essential parts):
image my-disk-image {
[...]
partition root {
image = "rootfs.ext4"
[...]
}
partition home {
image = "home.ext4"
[...]
}
}
image rootfs.ext4 {
[...]
mountpoint = "/"
}
image home.ext4 {
[...]
mountpoint = "/home"
}
Maybe a similar approach could be used in wic, too.
Best regards, Enrico
--
Pengutronix e.K. | Enrico Jörns |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-5080 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2016-11-23 8:40 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-22 9:05 Contents of non-rootfs partitions Kristian Amlie
[not found] ` <CA+4=imZLMh7di712mejxQ6qgsDSXiCOJJDbUY99YC9DoCrqrmQ@mail.gmail.com>
2016-11-22 9:54 ` Kristian Amlie
2016-11-22 11:10 ` Patrick Ohly
2016-11-22 11:54 ` Kristian Amlie
2016-11-23 8:40 ` Enrico Joerns [this message]
2016-11-23 9:04 ` Kristian Amlie
2016-11-23 9:24 ` Maciej Borzęcki
2016-11-23 10:12 ` Enrico Joerns
2016-11-23 11:03 ` Maciej Borzęcki
2016-11-23 12:08 ` Ed Bartosh
2016-11-23 13:08 ` Kristian Amlie
2016-11-23 13:22 ` Ed Bartosh
2016-11-23 13:51 ` Maciej Borzęcki
2016-11-23 14:10 ` Ed Bartosh
2016-11-23 15:56 ` Patrick Ohly
2016-11-24 6:15 ` Ulrich Ölmann
2016-11-24 7:38 ` Patrick Ohly
2016-11-24 7:38 ` Kristian Amlie
2016-11-24 13:23 ` Ed Bartosh
2016-11-24 14:43 ` Kristian Amlie
2016-11-24 14:51 ` Ed Bartosh
2016-11-24 15:24 ` Patrick Ohly
2016-11-24 15:52 ` Kristian Amlie
2016-11-24 15:28 ` Andreas Oberritter
2016-11-24 15:51 ` Kristian Amlie
2016-11-24 16:21 ` Patrick Ohly
2016-11-24 16:40 ` Kristian Amlie
2016-11-23 13:44 ` Ed Bartosh
2016-11-23 14:20 ` Kristian Amlie
2016-11-22 23:45 ` Khem Raj
2016-11-23 7:13 ` Kristian Amlie
2016-11-23 7:26 ` Khem Raj
2016-11-23 9:01 ` Kristian Amlie
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=776827b7-ca3e-e319-c2f0-b8b15bef4fb2@pengutronix.de \
--to=ejo@pengutronix.de \
--cc=eduard.bartosh@intel.com \
--cc=kristian.amlie@mender.io \
--cc=openembedded-core@lists.openembedded.org \
--cc=patrick.ohly@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).