From: "Steven J. Hill" <sjhill@cotw.com>
To: JFFS List <jffs-dev@axis.com>, MTD List <mtd@infradead.org>
Subject: Humble question on actual journalling mechanism...
Date: Sat, 23 Sep 2000 08:34:35 -0500 [thread overview]
Message-ID: <39CCB16B.976D39AF@cotw.com> (raw)
Greetings again.
I have been reading the JFFS code solid for the past two days
now. I am about 1/4 the way through 'intrep.c' which is just
huge. The function that I am currently looking at is
'jffs_insert_node'. I must humbly ask for how the underlying
journaling/versioning works. In the explanation, if the
manipulation of the members in the 'jffs_node' structure with
regards to versioning could be explained, that would be great.
All the other files were easy to understand because it was just
the basic calls for working with the flash and providing the
upper level functions for superblock and inode interfacing with
the kernel's VFS layer. 'intrep.c' is where the core is really
at and I would appreciate some simple understanding.
Yes, I did look through the MTD archives. No, I did not look
through the JFFS mailing list archives because they do not seem
to exist anywhere off of the Axis page or anywhere else for
that matter. I also apologize for the cross-post.
-Steve
--
Steven J. Hill - Embedded SW Engineer
Public Key: 'finger sjhill@mail.cotw.com'
FPR1: E124 6E1C AF8E 7802 A815
FPR2: 7D72 829C 3386 4C4A E17D
To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org
next reply other threads:[~2000-09-23 13:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-23 13:34 Steven J. Hill [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-09-24 10:12 Humble question on actual journalling mechanism Johan Adolfsson
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=39CCB16B.976D39AF@cotw.com \
--to=sjhill@cotw.com \
--cc=jffs-dev@axis.com \
--cc=mtd@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