From: Terence Soh <gopher@singnet.com.sg>
To: linux-mtd@lists.infradead.org
Subject: Cramfs on NAND
Date: Fri, 03 Mar 2006 09:37:40 +0800 [thread overview]
Message-ID: <44079DE4.3070804@singnet.com.sg> (raw)
In-Reply-To: <E1FErAE-00004u-2M@canuck.infradead.org>
Hi again,
I hear that cramfs on NAND flash is not a good idea because of the bad
blocks. Is this still true? There was talks some time ago about making
cramfs work on top on NAND.
<http://lists.infradead.org/pipermail/linux-mtd/2004-May/009784.html>
If this is true, are there any recommendations of what other fs to use.
I already have one partition of jffs2 to store read-write files.
Thanks again,
Terence.
next parent reply other threads:[~2006-03-03 2:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1FErAE-00004u-2M@canuck.infradead.org>
2006-03-03 1:37 ` Terence Soh [this message]
2006-03-10 13:06 ` Cramfs on NAND Josh Boyer
2006-03-10 17:36 ` Russ Dill
2006-03-13 0:34 ` Terence Soh
2006-03-18 2:43 ` Sean Kelley
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=44079DE4.3070804@singnet.com.sg \
--to=gopher@singnet.com.sg \
--cc=linux-mtd@lists.infradead.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.