From: Pantelis Antoniou <panto@intracom.gr>
To: tglx@linutronix.de
Cc: linux-mtd@lists.infradead.org
Subject: Re: Cram FS on NAND - How to do this?
Date: Thu, 12 Jun 2003 11:15:58 +0300 [thread overview]
Message-ID: <3EE836BE.4030909@intracom.gr> (raw)
In-Reply-To: <200306121106.09768.tglx@linutronix.de>
Thomas Gleixner wrote:
>On Wednesday 11 June 2003 10:43, Pantelis Antoniou wrote:
>
>>Hi
>>
>>I have a requirement to have a compressed read only
>>root filesystem in my board and I've come to the
>>conclussion that the best fit would be CRAMFS if only
>>had any concept of bad blocks.
>>
>
>Why don't you use a JFFS2 partition and mount it read only ?
>Then you have a compressed read only root filesystem.
>All there no hacking required. :)
>
>
Well JFFS2 is a wonderful filesystem, but it does have it's
detractions.
The main problem with it is the time it spends on mount when
scanning the device; the larger the device, the larger the time.
Also the compression ratio's of CRAMFS are better.
You should use the right tool for the job.
And what's wrong with a little bit of hacking ehh? :-)
Regards
Pantelis
next prev parent reply other threads:[~2003-06-12 8:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-11 8:43 Cram FS on NAND - How to do this? Pantelis Antoniou
2003-06-11 8:51 ` David Woodhouse
2003-06-11 8:58 ` Pantelis Antoniou
2003-06-11 9:04 ` David Woodhouse
2003-06-11 9:10 ` Russ Dill
2003-06-11 9:12 ` David Woodhouse
2003-06-11 9:01 ` Jasmine Strong
2003-06-11 9:54 ` Pantelis Antoniou
2003-06-11 10:24 ` angainor
2003-06-11 19:22 ` Russ Dill
2003-06-12 8:22 ` Pantelis Antoniou
2003-06-12 9:06 ` Thomas Gleixner
2003-06-12 8:15 ` Pantelis Antoniou [this message]
2003-06-12 23:13 ` Charles Manning
2003-06-13 12:18 ` Jasmine Strong
2003-06-13 16:30 ` Brian J. Fox
2003-06-13 16:33 ` Jasmine Strong
2003-06-13 16:45 ` Brian J. Fox
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=3EE836BE.4030909@intracom.gr \
--to=panto@intracom.gr \
--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