public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Tim Riker <Tim@Rikers.org>
Cc: "Jose Rodr�guez Argente" <jradc@tid.es>, linux-mtd@lists.infradead.org
Subject: Re: Read Only FS
Date: Tue, 16 Oct 2001 06:26:01 +0100	[thread overview]
Message-ID: <18185.1003209961@redhat.com> (raw)
In-Reply-To: <3BCB8F35.61CC1A8B@Rikers.org>

Having a large romfs and then a relatively small jffs2 will make it boot 
faster, because the jffs2 scan obviously doesn't have as much to do. But 
you won't get the wear levelling - obviously the R/W bits are then limited 
to the area of flash that you partitioned for jffs2. 

romfs will work happily on /dev/mtdblock<n> devices, either the full 
CONFIG_MTD_BLOCK device which would also allow you to update the contents 
(as long as it's not mounted at the time, of course) or the smaller 
CONFIG_MTD_BLOCK_RO module which provides the same device, just without 
write functionality.

--
dwmw2

  reply	other threads:[~2001-10-16  5:16 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
2001-10-16  5:26   ` David Woodhouse [this message]
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=18185.1003209961@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox