From: Wolfgang Denk <wd@denx.de>
To: "Chantara Thlang" <thlang@iphase.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: need arguments to use JFFS2
Date: Fri, 06 Dec 2002 11:34:15 +0100 [thread overview]
Message-ID: <20021206103420.76729C614B@atlas.denx.de> (raw)
In-Reply-To: Your message of "Fri, 06 Dec 2002 11:10:28 +0100." <049e01c29d0f$b3c52ff0$221faf9d@iphase.com>
Dear Chantara,
in message <049e01c29d0f$b3c52ff0$221faf9d@iphase.com> you wrote:
>
> In the web, I am not sure to see an article which clearly express the
> advantage of JFFS2.
It makes little sense to dicuss "advantages" without specifying
requirements.
> Please could someone give me some arguments to use JFFS2 instead of all
> others Flash FS such as CRAMFS ?
One significant advantage is that JFFS2 provides a _writable_ flash
filesystem, while cramfs is read-only. But as stated before: this is
an advantage only when you need a writable filesystem.
> One of the reason could it be in the Flash management : optimization ?
Yes.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
Every program has at least one bug and can be shortened by at least
one instruction - from which, by induction, one can deduce that every
program can be reduced to one instruction which doesn't work.
next prev parent reply other threads:[~2002-12-06 10:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-06 10:10 need arguments to use JFFS2 Chantara Thlang
2002-12-06 10:34 ` Wolfgang Denk [this message]
2002-12-06 10:42 ` David Woodhouse
2002-12-07 8:35 ` Charles Manning
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=20021206103420.76729C614B@atlas.denx.de \
--to=wd@denx.de \
--cc=linux-mtd@lists.infradead.org \
--cc=thlang@iphase.com \
/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