From: Artem Bityutskiy <dedekind@infradead.org>
To: darshak@elitecore.com
Cc: linux-mtd@lists.infradead.org
Subject: Re: starter!
Date: Sat, 18 Nov 2006 14:51:50 +0200 [thread overview]
Message-ID: <1163854310.5597.62.camel@sauron> (raw)
In-Reply-To: <2785.192.168.15.61.1163841555.squirrel@newwebmail.elitecore.com>
Hi,
On Sat, 2006-11-18 at 14:49 +0530, darshak@elitecore.com wrote:
> Hi All
> I want to involve in JFFs3 development.
> Please tell me what is required docs/knowledge for that.
> How can I proceed for that ?
I guess you may start from the JFFS3 docs available at
http://www.linux-mtd.infradead.org/tech/JFFS3design.pdf
It is quite old and we changed our minds about several things.
You may also read Szeged guys docs at
http://www.inf.u-szeged.hu/jffs2/jffs3.php
But the last plan is to base JFFS3 on top of UBI which is a new
promising piece of software. Look at
http://www.linux-mtd.infradead.org/doc/ubi.html
http://www.linux-mtd.infradead.org/faq/ubi.html
So, to put it differently, there is no cool and clean documentation.
There is some code and prototypes but they are far from something usable
yet. But if you are eager enough you withstand this :-)
Alternatively, there is a LogFS project, see
http://www.linux-mtd.infradead.org/doc/logfs.html
I do not follow it but there is some code exist. You may be interested.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2006-11-18 12:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-18 9:19 starter! darshak
2006-11-18 12:51 ` Artem Bityutskiy [this message]
2006-11-20 4:39 ` starter! Darshak
2006-11-20 7:34 ` starter! Artem Bityutskiy
[not found] <6AD9F6A5F6E096408F0B703773355A07016BBA00@CHN-SNR-MBX01.wipro.com>
2006-11-20 5:09 ` starter! Darshak
2006-11-20 7:48 ` starter! Artem Bityutskiy
2006-11-20 9:01 ` starter! Darshak
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=1163854310.5597.62.camel@sauron \
--to=dedekind@infradead.org \
--cc=darshak@elitecore.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