From: Artem Bityutskiy <dedekind@yandex.ru>
To: Corentin Chary <corentincj@iksaif.net>
Cc: linux-fsdevel@vger.kernel.org,
HIBLOT Jean-Jacques <jjhiblot@adeneo.adetelgroup.com>,
Gregory CLEMENT <gclement@adeneo.adetelgroup.com>,
linux-mtd@lists.infradead.org
Subject: Re: Request for review: NandFS
Date: Fri, 06 Feb 2009 09:50:32 +0200 [thread overview]
Message-ID: <498BEBC8.3000302@yandex.ru> (raw)
In-Reply-To: <200902031327.59536.corentincj@iksaif.net>
Corentin Chary wrote:
> Hi,
> Here is NandFS, a NAND Flash Filesystem.
> NandFS is similar to YAFFS2 (in some ways), but the codebase is much more
> cleaner and simpler. And we'll try to go mainline.
>
> Development started at Adeneo (http://www.adeneo-embedded.com/srt/en/home) in
> 2007. After a long pause, I re-started to clean the code in october 2008.
>
> With the new UBIFS, we might think than there is no room for another flash
> filesystem. But another GPLed filesystem can't hurt anyone. Some of us may
> have heard some words about UFFS, but this project is in no way related to
> NandFS.
>
> *IMPORTANT*: NandFS is under active development, and can't be considered safe
> or stable !
Probably you have a very good motivation to do work from
scratch, but what is sad that instead of joining us and
improving UBI/UBIFS stack, you spend your time creating new
file-system.
Almost nobody is interested in new unscalable solutions, and
you really waste your time, because we already have 3 of them,
at least.
There are so many things to improve in UBI/UBIFS, and there
is a possibility to create a scalable UBI2. You may do a lot
of exciting things in the area, instead.
Please, think about joining us instead :-)
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2009-02-06 7:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-03 12:27 Request for review: NandFS Corentin Chary
2009-02-06 7:50 ` Artem Bityutskiy [this message]
2009-02-06 13:52 ` Bill Gatliff
2009-02-07 11:27 ` Corentin Chary
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=498BEBC8.3000302@yandex.ru \
--to=dedekind@yandex.ru \
--cc=corentincj@iksaif.net \
--cc=gclement@adeneo.adetelgroup.com \
--cc=jjhiblot@adeneo.adetelgroup.com \
--cc=linux-fsdevel@vger.kernel.org \
--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