From: Russ Dill <Russ.Dill@asu.edu>
To: Henrik Nordstrom <hno@marasystems.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Srinivasu.Vaduguri@nokia.com, linux-mtd@lists.infradead.org
Subject: Re: CRAMFS on MTD/NAND Issue
Date: 09 Jan 2003 12:07:48 -0700 [thread overview]
Message-ID: <1042139267.10724.34.camel@timmy> (raw)
In-Reply-To: <Pine.LNX.4.44.0301090206130.14735-100000@filer.marasystems.com>
On Wed, 2003-01-08 at 18:08, Henrik Nordstrom wrote:
> On Wed, 8 Jan 2003, Thomas Gleixner wrote:
>
> > Mount your rootfs _readonly_ and you have the _same_ including bad block
> > handling.
>
> If a flag could be added to a jffs2 image denying it to be mounted
> read-write then yes..
>
I might reiterate that the end goal of cramfs is efficency, and decent
speed. The end goal of jffs2 is quite different (although it still
strives for those things). iirc, cramfs images usually end up being 5%
to 10% smaller than jffs2 images, they boot a lot faster, the code is a
lot smaller (especially helpfull if you want fs support in your
bootloader)
--
Russ Dill <Russ.Dill@asu.edu>
next prev parent reply other threads:[~2003-01-09 18:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-08 12:40 CRAMFS on MTD/NAND Issue Srinivasu.Vaduguri
2003-01-08 19:42 ` Russ Dill
2003-01-08 20:27 ` Thomas Gleixner
2003-01-08 20:51 ` Henrik Nordstrom
2003-01-08 22:04 ` Thomas Gleixner
2003-01-09 1:08 ` Henrik Nordstrom
2003-01-09 19:07 ` Russ Dill [this message]
2003-01-08 20:33 ` Henrik Nordstrom
2003-01-08 20:46 ` Russ Dill
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=1042139267.10724.34.camel@timmy \
--to=russ.dill@asu.edu \
--cc=Srinivasu.Vaduguri@nokia.com \
--cc=hno@marasystems.com \
--cc=linux-mtd@lists.infradead.org \
--cc=tglx@linutronix.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