Linux-mtd Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rod Campbell <rod.campbell@telosalliance.com>
To: <linux-mtd@lists.infradead.org>
Subject: Read-only file systems using NAND/MTD
Date: Mon, 24 Nov 2014 15:41:08 -0500	[thread overview]
Message-ID: <006d01d00826$fa33c2a0$ee9b47e0$@TelosAlliance.com> (raw)

Hello,

Is there an update about implementing a read-only file system on NAND?  The
most recent discussion I could find was from May 2012:  

http://lists.infradead.org/pipermail/linux-mtd/2012-May/041200.html

The conclusion seemed to be to use ubi underneath something like squashfs to
provide bad-block awareness.  Is this still the recommended solution?  

Thanks,
Rod Campbell

>From the desk of:
Rod Campbell
Senior Software Engineer
Linear Acoustic Inc.
108 Foxshire Drive, Lancaster PA 17601
Tel: 717-735-3611
Fax: 717-735-3612
E-mail: Rod.Campbell@TelosAlliance.com
www.linearacoustic.com

             reply	other threads:[~2014-11-24 20:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-24 20:41 Rod Campbell [this message]
2014-11-24 21:21 ` Read-only file systems using NAND/MTD Richard Weinberger
2014-11-24 21:28   ` Brian Norris

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='006d01d00826$fa33c2a0$ee9b47e0$@TelosAlliance.com' \
    --to=rod.campbell@telosalliance.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox