All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Riker <Tim@Rikers.org>
To: "Jose Rodr�guez Argente" <jradc@tid.es>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Read Only FS
Date: Mon, 15 Oct 2001 19:36:53 -0600	[thread overview]
Message-ID: <3BCB8F35.61CC1A8B@Rikers.org> (raw)
In-Reply-To: 3BCAED35.3000309@tid.es

three main choices:

romfs, cramfs, jffs2

romfs is uncompressed and so does not need to decompress.

cramfs is compressed and indexed, and so has shorter boot time

jffs2 is compressed but must do a full scan on bootup. It can be
read/write.

Consider that flash reads may actually take longer than decompression
depending on your hardware. I'd recommend a single jffs2 partition for
most applications. This is the best use of a small amount of flash.
Mount it readonly most of the time if you like and have some way to
snapshot the current config data that remounts read-write, saves, and
then remounts read-only. I have often made /var ramfs with /tmp ->
/var/tmp, and /dev -> /var/dev so that writes can happen there. Then the
bootup script fully populate /var.

Jose Rodríguez Argente wrote:
> 
> Hello,
> 
>    I am working on an Assabet platform. My application will have a
> significant part of the root filesystem mounted as read-only. I am
> thinking about installing it as romfs, which I think should be faster
> than JFFS2. Am I right?
> 
> Another question is wether romfs runs over MTD or it has its own access
> layer.
> 
> Thank you very much
> 
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/

-- 
Tim Riker - http://rikers.org/ - short SIGs! <g>
All I need to know I could have learned in Kindergarten
... if I'd just been paying attention.

  reply	other threads:[~2001-10-16  1:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-15 14:05 Read Only FS Jose Rodríguez Argente
2001-10-16  1:36 ` Tim Riker [this message]
2001-10-16  5:26   ` David Woodhouse
2001-10-16 16:29     ` Question/suggestion Joakim Tjernlund
2001-10-16 16:37       ` Question/suggestion David Woodhouse
2001-10-17  6:43         ` Question/suggestion Joakim Tjernlund
2001-10-17  8:00           ` Question/suggestion David Woodhouse
2001-10-18 10:00             ` Question/suggestion Joakim Tjernlund
2001-10-18 10:09               ` Question/suggestion David Woodhouse
2001-10-18 10:27                 ` Question/suggestion Joakim Tjernlund
2001-10-18 10:38                   ` Question/suggestion David Woodhouse
2001-10-18 14:15                     ` Question/suggestion Joakim Tjernlund
2001-10-18 14:16                       ` Question/suggestion David Woodhouse
2001-11-02 11:37       ` Question/suggestion Joakim Tjernlund

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=3BCB8F35.61CC1A8B@Rikers.org \
    --to=tim@rikers.org \
    --cc=jradc@tid.es \
    --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.