From: Manish Katiyar <mkatiyar@gmail.com>
To: Dave Kleikamp <shaggy@linux.vnet.ibm.com>
Cc: Alberich de megres <alberich2k5@gmail.com>,
linux-fsdevel@vger.kernel.org
Subject: Re: root dir
Date: Tue, 10 Feb 2009 18:03:49 +0530 [thread overview]
Message-ID: <ea11fea30902100433h2f23abi16e4e5e1b32d5934@mail.gmail.com> (raw)
In-Reply-To: <1234269006.19392.4.camel@norville.austin.ibm.com>
On Tue, Feb 10, 2009 at 6:00 PM, Dave Kleikamp
<shaggy@linux.vnet.ibm.com> wrote:
> On Tue, 2009-02-10 at 13:18 +0100, Alberich de megres wrote:
>> thanks Dave :)
>>
>> I didn't know about rkfs..
>>
>> is there some other place that gives a deep loop to vfs?
>
> Definitely take a look at Documentation/vfs.txt in the kernel source
> tree. It contains some pointers to some not-quite-up-to-date articles
> on writing file systems.
>
>> and what about journaling?
Being a newbie myself, I think the best way to understand journalling
would be to understand first its structure and then read jbd/jbd2
codepath. And to understand structure easiest thing is to read the
code of debugfs (which comes with e2fsprogs) or if you are comfortable
with C++ (unlike me :( ), read the source code of ext3grep.
Thanks -
Manish
>
> I'm not sure what's out there.
>
>> :)
>
> Good luck!
>
> Shaggy
> --
> David Kleikamp
> IBM Linux Technology Center
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2009-02-10 12:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 13:54 root dir Alberich de megres
2009-02-09 22:05 ` Dave Kleikamp
2009-02-10 12:18 ` Alberich de megres
2009-02-10 12:30 ` Dave Kleikamp
2009-02-10 12:33 ` Manish Katiyar [this message]
2009-02-11 21:45 ` Alberich de megres
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=ea11fea30902100433h2f23abi16e4e5e1b32d5934@mail.gmail.com \
--to=mkatiyar@gmail.com \
--cc=alberich2k5@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=shaggy@linux.vnet.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).