public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Daniel Toussaint <daniel@arbor.com.tw>
To: Mtd <linux-mtd@lists.infradead.org>
Subject: compact flash and jffs2
Date: Thu, 5 Sep 2002 18:40:08 +0800	[thread overview]
Message-ID: <200209051840.08265.daniel@arbor.com.tw> (raw)

Hi all, 

So far I've always been using compact flash as a regular IDE device, putting 
cramfs for read-only, ext2 for r/w partitions. 
I was wondering if using the blkmtd device with a jffs2 filesystem would be a 
better way for R/W partitions ? 
On diverse mailling lists, there are contradicting answers. Some say it's THE 
way to use CF cards, others say it's totally useless since CF cards have 
their own wear leveling system build in. 
There were reports that it takes forever to mount a cf card with blkmtd/jffs2. 
I've tried it, it does take a long time for the whole cf, but in smaller 
partitions (2 - 3 M) it's acceptable. 

questions: 
* So, is it wise, to use a setup like that in a system, let's say to update 
system configuration files on a small , sepate partition ? 
* Are there some parameters that I can give to blkmtd.o to speed up the 
process of mounting? Currently I only give it "device=/dev/.." 
* Is it better to compile blkmtd.o in the kernel, or leave it as a  module? .

Thanks, 

Greetings,
Daniel



-- 
ARBOR Technology Corp.		   	Industrial PC-based Automation
_______________________________________________________________________

Address :  5F, No 738 Zhong Zheng Rd., Zhong He, Taipei, Taiwan
Tel     :  886 2 8226 9396   ext : 652
Fax     :  886 2 8226 9398


WWW pages  :  http://www.arbor.com.tw 

an ISO-9001 certified company

                 reply	other threads:[~2002-09-05 10:37 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200209051840.08265.daniel@arbor.com.tw \
    --to=daniel@arbor.com.tw \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox