From: Theodore Ts'o <tytso@mit.edu>
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] Is there a particular reason cerowrt isn't using UBIFS?
Date: Sat, 30 Aug 2014 17:34:51 -0400 [thread overview]
Message-ID: <20140830213451.GA30271@thunk.org> (raw)
Potentially stupid question. I was taking a look at
http://wiki.openwrt.org/doc/techref/filesystems
and there was discussion there about how using raw squashfs doesn't
deal with wear leveling and bad flash blocks, and that openwrt is now
using ubifs for all targets with raw NAND flash --- and my
understanding is that the WNDR 3800 uses raw NAND flash. Is there any
particular reason why Cerowrt isn't using ubifs, or squashfs over ubi,
other than purely historical and/or this wasn't the research focus of Cerowrt?
Thanks,
- Ted
next reply other threads:[~2014-08-30 21:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-30 21:34 Theodore Ts'o [this message]
2014-08-30 21:57 ` Dave Taht
2014-08-31 1:38 ` Theodore Ts'o
2014-08-31 7:05 ` David Lang
2014-08-31 16:45 ` Theodore Ts'o
2014-08-31 17:29 ` Dave Taht
2014-08-31 19:37 ` David Lang
2014-08-31 22:03 ` Theodore Ts'o
2014-08-31 16:58 ` Dave Taht
2014-08-31 7:01 ` David Lang
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
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140830213451.GA30271@thunk.org \
--to=tytso@mit.edu \
--cc=cerowrt-devel@lists.bufferbloat.net \
/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