mtd/fs/jffs3 JFFS3design.tex,1.13,1.14

Artem Bityuckiy dedekind at infradead.org
Sat Jan 29 06:42:30 EST 2005


Update of /home/cvs/mtd/fs/jffs3
In directory phoenix.infradead.org:/tmp/cvs-serv23109

Modified Files:
	JFFS3design.tex 
Log Message:
Minor fixes


Index: JFFS3design.tex
===================================================================
RCS file: /home/cvs/mtd/fs/jffs3/JFFS3design.tex,v
retrieving revision 1.13
retrieving revision 1.14
diff -u -r1.13 -r1.14
--- JFFS3design.tex	29 Jan 2005 11:27:16 -0000	1.13
+++ JFFS3design.tex	29 Jan 2005 11:42:28 -0000	1.14
@@ -102,9 +102,9 @@
 
 \raggedright \emph{Node}
 &
-Basic JFFS3 data structure - anything which JFFS3 stores on flash is
+Basic JFFS3 data structure -- anything which JFFS3 stores on flash is
 stored in form of nodes. There are different types of nodes defined.
-Nodes have standard layout - common header, header and
+Nodes have standard layout -- common header, header and
 data. Common header is the same for any node type. Header and
 data sections are different for different node types.
 \\[4pt]
@@ -208,11 +208,11 @@
 Two JFFS3 checksum working modes are defined and
 depending on the file type and device's goal, one of them is used.
 \begin{enumerate}
-\item \emph{Strict mode} - JFFS3 writes and always checks node's
+\item \emph{Strict mode} -- JFFS3 writes and always checks node's
 checksums. For example, it makes sense to use this checksum mode for sensitive files
 like system libraries or if for different reasons if it is needed to
 detect errors as early as possible.
-\item \emph{Relaxed mode} - JFFS3 writes, but does not check
+\item \emph{Relaxed mode} -- JFFS3 writes, but does not check
 checsums when nodes are being read. It makes sense to use this mode on
 very reliable flashes like NOR.
 \end{enumerate}
@@ -323,7 +323,7 @@
 generated nor checked.\\
 \url{http://lists.infradead.org/pipermail/linux-mtd/2005-January/011640.html}.
 
-\item Have special type of notes where we may store static inode node's
+\item Have special type of nodes where we may store static inode node's
 (and may be other's) attributes like UID and GID. Perhaps, the xattr
 support may be used here.\\
 \url{http://lists.infradead.org/pipermail/linux-mtd/2005-January/011615.html}.





More information about the linux-mtd-cvs mailing list