From: David Woodhouse <dwmw2@infradead.org>
To: Joakim Tjernlund <joakim.tjernlund@transmode.se>
Cc: "Thorsten Mühlfelder" <muehlfelder@enertex.de>,
linux-mtd@lists.infradead.org
Subject: Re: How stable is jffs2 summarize option?
Date: Tue, 01 Jun 2010 11:38:57 +0100 [thread overview]
Message-ID: <1275388737.25797.89.camel@macbook.infradead.org> (raw)
In-Reply-To: <OF6BA924CE.75C9F3A4-ONC1257735.0035A313-C1257735.00360683@transmode.se>
On Tue, 2010-06-01 at 11:50 +0200, Joakim Tjernlund wrote:
> >
> > On Tue, 2010-06-01 at 11:26 +0200, Thorsten Mühlfelder wrote:
> > > and what do you think about switching to yaffs2? I know it is developed
> > > elsewhere, but it seems to be a good alternative to jffs2+summary and
> > > probably switching is easier than to ubifs.
> >
> > Why would you think that switching to something that isn't part of the
> > Linux kernel would be easier than switching to ubifs? That seems... odd.
>
> Yes, if ubifs doesn't fit, perhaps have a look at the recently added
> logfs?
>
> Jocke
>
> BTW, I once tried JFFS2 summary and it didn't make much of a difference for us.
Did you use 'sumtool' after creating your images? For reasons which are
now lost in the mists of time, that support wasn't just added directly
to mkfs.jffs2.
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@intel.com Intel Corporation
next prev parent reply other threads:[~2010-06-01 10:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-31 13:03 How stable is jffs2 summarize option? Thorsten Mühlfelder
2010-05-31 15:17 ` Thorsten Mühlfelder
2010-05-31 20:00 ` Vitaly Wool
2010-05-31 19:59 ` Vitaly Wool
2010-06-01 7:28 ` Thorsten Mühlfelder
2010-06-01 10:05 ` Ladislav Michl
2010-06-01 9:15 ` David Woodhouse
2010-06-01 9:26 ` Thorsten Mühlfelder
2010-06-01 9:33 ` David Woodhouse
2010-06-01 9:50 ` Joakim Tjernlund
2010-06-01 10:07 ` Thorsten Mühlfelder
2010-06-01 10:38 ` David Woodhouse [this message]
2010-06-01 11:39 ` Joakim Tjernlund
2010-06-01 10:03 ` Thorsten Mühlfelder
2010-06-01 9:47 ` Vitaly Wool
2010-06-01 10:13 ` Thorsten Mühlfelder
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=1275388737.25797.89.camel@macbook.infradead.org \
--to=dwmw2@infradead.org \
--cc=joakim.tjernlund@transmode.se \
--cc=linux-mtd@lists.infradead.org \
--cc=muehlfelder@enertex.de \
/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).