All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Henrik Nordstrom <hno@marasystems.com>
Cc: Russ Dill <Russ.Dill@asu.edu>,
	Srinivasu.Vaduguri@nokia.com, linux-mtd@lists.infradead.org
Subject: Re: CRAMFS on MTD/NAND Issue
Date: Wed, 08 Jan 2003 23:04:25 +0100	[thread overview]
Message-ID: <200301082304.25101.tglx@linutronix.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0301082150360.9902-100000@filer.marasystems.com>

On Wednesday 08 January 2003 21:51, Henrik Nordstrom wrote:
> On Wed, 8 Jan 2003, Thomas Gleixner wrote:
> > > roll your own: Please, make a static compressed filesystem (like
> > > cramfs) that incorporates extra blocks, so that when the checksum is
> > > bad while initially writing the filesystem, or reading the file system
> > > (in the case where ecc can save the data), it rewrites this block to a
> > > free sector). It would seem like a simple modification to cramfs to me.
> >
> > Don't reinvent the wheel! :)
>
> Having a image based filesystem which cannot be written to has it's
> beauty..
Mount your rootfs _readonly_ and you have the _same_ including bad block 
handling.

-- 
Thomas
________________________________________________________________________
linutronix - competence in embedded & realtime linux
http://www.linutronix.de
mail: tglx@linutronix.de

  reply	other threads:[~2003-01-08 21:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-08 12:40 CRAMFS on MTD/NAND Issue Srinivasu.Vaduguri
2003-01-08 19:42 ` Russ Dill
2003-01-08 20:27   ` Thomas Gleixner
2003-01-08 20:51     ` Henrik Nordstrom
2003-01-08 22:04       ` Thomas Gleixner [this message]
2003-01-09  1:08         ` Henrik Nordstrom
2003-01-09 19:07           ` Russ Dill
2003-01-08 20:33   ` Henrik Nordstrom
2003-01-08 20:46     ` Russ Dill

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=200301082304.25101.tglx@linutronix.de \
    --to=tglx@linutronix.de \
    --cc=Russ.Dill@asu.edu \
    --cc=Srinivasu.Vaduguri@nokia.com \
    --cc=hno@marasystems.com \
    --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.