From: "Vitus Jensen" <vjensen@gmx.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: bitbaking aufs
Date: Wed, 24 Aug 2011 11:38:02 +0200 [thread overview]
Message-ID: <20110824093802.194230@gmx.net> (raw)
In-Reply-To: <201108241102.05565.ml@vdm-design.de>
On Wed, 24 Aug 2011 11:02:05 +0200 Thomas Zimmermann wrote:
> On Wednesday, August 24, 2011 00:11:39 Vitus Jensen wrote:
> > Hej!
> >
> > I would like to use a layered filesystem in our ppc603e-based machine:
> > the rootfs built from openembedded would be read-only, any
> > customizations go to a writable filesystem and should the need
> > occur to start fresh all I
> > need is a mechanism to remove the contents of the writable filesystem.
> >
> > In openembedded (2011.03) there is unionfs and aufs
> > (http://aufs.sourceforge.net/), aufs is more actively developed so
> > I would like to use that. Unfortunately the recipe in oe uses
> > aufs1 which does
> > not support current kernels. Could change that to aufs2.2 but
> > aufs2 now has two seperated repos (patched kernel or source plus
> > patches = "standalone") and I'm in doubt how to proceed.
> > Especially as aufs_cvs.bb contains some CONFIG_xxx voodo.
> >
> > My intention is to use the "standalone" repo and "inherit module"
> > from oe
> > but how do I apply kernel patches in this case? The kernel resides in
> > ${TMPDIR}/sysroots, do I patch that??? Or do I have to apply those
> > patches during kernel build? I could extract them from git and add
> > them to the kernel recipe for my machine but this doesn't feel right,
...
> You have to patch the kernel to export a lot of symbols for aufs2.
> So you have to rebuild the kernel anyway. And then i think it
> would be the easiest way if you integrate it into your kernel
> directly. Like described in the README section 3.1.
>
> In my opinion a standalone aufs recipe is not possible, because the
> kernel needs to be patched and you have to use the specific branch
> for your kernel version.
In this case (and in the meantime I came to the same conclusion) it is easiest to use the already patched kernel tree from aufs.sourceforge, create a linux-aufs_2.6.36.bb and use that for my device. Or have a second look to union-mount (http://valerieaurora.org/union/) and build a recipe for that tree.
Thank you for your viewpoints, they helped.
Vitus
--
NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurück-Garantie!
Jetzt informieren: http://www.gmx.net/de/go/freephone
next prev parent reply other threads:[~2011-08-24 9:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-23 22:11 bitbaking aufs Vitus Jensen
2011-08-24 9:02 ` Thomas Zimmermann
2011-08-24 9:38 ` Vitus Jensen [this message]
2011-09-07 4:45 ` Vitus Jensen
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=20110824093802.194230@gmx.net \
--to=vjensen@gmx.de \
--cc=openembedded-devel@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 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.