From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: Kristian Amlie <kristian.amlie@mender.io>
Cc: Eduard Bartosh <eduard.bartosh@intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: Contents of non-rootfs partitions
Date: Wed, 23 Nov 2016 15:44:04 +0200 [thread overview]
Message-ID: <20161123134404.GC13863@linux.intel.com> (raw)
In-Reply-To: <5064cacc-e724-c7b8-9631-3d961c5a29f6@mender.io>
On Wed, Nov 23, 2016 at 02:08:28PM +0100, Kristian Amlie wrote:
> On 23/11/16 13:08, Ed Bartosh wrote:
> > On Tue, Nov 22, 2016 at 12:54:52PM +0100, 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!
> >>
> >>> To implement this approach with wic, wic needs to be taught how to
> >>> exclude directories from the main rootfs. Ideally, the mkfs.* tools
> >>> should also support that without having to make an intermediate copy of
> >>> the files for a certain partition, but initially wic could create
> >>> temporary directory trees.
> >>
> >> Yes, some work would be needed here, but ultimately it would be contained within wic and related tools, which is a good thing.
> >>
> >
> > I support the idea. Let's discuss the details of implementation and
> > create a bug in bugzilla to track the development
>
> Do you want me to create the ticket? (it'll be my first, so apologies in
> advance if I omit something important)
>
Yes, please create an issue in bugzilla and assign it to me. Don't
worry. If you miss something other people will point to in in the
comments :)
--
Regards,
Ed
next prev parent reply other threads:[~2016-11-23 13:44 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
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 [this message]
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=20161123134404.GC13863@linux.intel.com \
--to=ed.bartosh@linux.intel.com \
--cc=eduard.bartosh@intel.com \
--cc=kristian.amlie@mender.io \
--cc=openembedded-core@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox