From: Hamish Moffatt <hamish@cloud.net.au>
To: linux-mtd@lists.infradead.org
Subject: ext2 for read-only file system on UBI
Date: Mon, 19 May 2008 16:21:49 +1000 [thread overview]
Message-ID: <20080519062149.GA16462@cloud.net.au> (raw)
My embedded device has a read-only root file system which is only
replaced by writing a whole image (dd, flashcp, ubiupdatevol etc).
Using gluebi and mtdblock, I think I can put a traditional block file
system (eg ext2) on top of NAND flash. What are the disadvantages of
this? (For the read-only application only.)
Background: I've got older hardware which uses ext2 on top of compact
flash in IDE mode, and new hardware which has replaced the compact flash
with NAND. I'd like to share an ext2 image between the two if possible.
The read-write file systems use ubifs. I'm only considering this for the
read-only volumes. One obvious disadvantage is lack of compression. Are
there others? Do I still get the reliability of ubi?
ie what does "UBI is not an FTL" mean in practice?
thanks,
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
next reply other threads:[~2008-05-19 6:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-19 6:21 Hamish Moffatt [this message]
2008-05-19 6:37 ` ext2 for read-only file system on UBI Artem Bityutskiy
2008-05-19 6:56 ` Hamish Moffatt
2008-05-19 7:08 ` Artem Bityutskiy
2008-05-19 7:44 ` Hamish Moffatt
2008-05-19 7:54 ` Artem Bityutskiy
2008-05-19 7:57 ` Artem Bityutskiy
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=20080519062149.GA16462@cloud.net.au \
--to=hamish@cloud.net.au \
--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