From: "Mike (mwester)" <mwester@dls.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: union fs
Date: Mon, 14 Apr 2008 15:55:04 -0500 [thread overview]
Message-ID: <4803C4A8.2090000@dls.net> (raw)
In-Reply-To: <E1JlVDo-0001Q4-Vo@daffy.sipo.nl>
RvP wrote:
> From: "Mike (mwester)" <mwester@dls.net>
>> RvP wrote:
>>> Hi,
>>>
>>> Support for unionfs-modules with recent kernels is broken in oe, see
>>> http://bugs.openembedded.org/show_bug.cgi?id=1189.
>>>
>>> Are there plans to fix this?
>> The unionfs modules are part of the 2.6 kernel now.
>
> Are they? I read on the unionfs site that they are part of the -mm tree as of
> Jan. 2007, but, you're probably right. OpenWRT does use unionfs per default
> with a 2.6.24 kernel.
No, you're right - I looked more closely, it's still not made it into
the 2.6.24 kernel.
>> Do you really need them?
>
> Not anymore, I was looking for a way to install extra pakages for SlugOS on
> an external drive. I found in the docs that a copy of the complete rootfs can
> be installed on an external drive using 'turnup' (NSLU2 specific tool). I'll
> go that way.
>
> Thanks,
>
> Richard.
Cool. Turnup is the right way to do it with SlugOS. But I do still
plan to get unionfs into the SlugOS feeds at some point. It does look
like at the moment that means fixing that recipe somehow; something that
won't be simple (since the patch downloaded depends on the kernel
version the recipe is being built for).
Thanks,
Mike (mwester)
next prev parent reply other threads:[~2008-04-14 20:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-14 20:24 union fs RvP
2008-04-14 20:55 ` Mike (mwester) [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-04-14 12:12 RvP
2008-04-14 16:49 ` Mike (mwester)
2008-04-15 8:36 ` Szabolcs Szakacsits
2008-04-15 15:31 ` Mike (mwester)
2008-04-15 21:48 ` Szabolcs Szakacsits
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=4803C4A8.2090000@dls.net \
--to=mwester@dls.net \
--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.