patch-2.1.107 linux/Documentation/filesystems/vfs.txt

• Lines: 41
• Date: Wed Jun 24 14:30:07 1998
• Orig file: v2.1.106/linux/Documentation/filesystems/vfs.txt
• Orig date: Thu May 7 22:51:46 1998

diff -u --recursive --new-file v2.1.106/linux/Documentation/filesystems/vfs.txt linux/Documentation/filesystems/vfs.txt
@@ -2,22 +2,22 @@
 ===========================================
 	by Benjamin LaHaise (blah@dot.superaje.com)
 
-Noone else seems to be writing this, so here's a quick description of what
-I've learned while writing lofs...
+No one else seems to be writing this, so here's a quick description of what
+I've learned while writing lofs.
 
 The VFS is relatively simple, but it is nice not to have to browse through
 pages of code to determine what is expected when writing a filesystem.
-Hopefully this helps anyone attempting such a feat, as well as clearing up
-a few important points/dependencies.
+This document is meant to help anyone attempting such a feat, and to clarify 
+a few important points and dependencies.
 
 register_filesystem (struct file_system_type *fstype)
 =====================================================
 
-All filesystems are created equal... or at least they start out that way.
-A filesystem, be it in module form, or linked into the kernel, needs to add
+All filesystems are created equal, or at least they start out that way.
+A filesystem, whether in module form or linked into the kernel, needs to add
 itself to the table of filesystems by calling register_filesystem with an
 initialized file_system_type structure.  Any further functions of the
-filesystem are accessed through the following function tables...
+filesystem are accessed through the following function tables:
 
 
 struct file_system_type
@@ -101,8 +101,8 @@
 	int (*lookup) (struct inode *dir, const char *name, int len, struct inode **result);
 	[optional]
 		lookup is called when the VFS wishes to have the filesystem resolve a name
-		into an inode.  Dir is a directory on the filesystem that [hopefully] contains
-		the zero terminated string name (length len).  A return value of zero indicates
+		into an inode.  Dir is a directory on the filesystem that--we hope--contains
+		the zero-terminated string name (length len).  A return value of zero indicates
 		that there is a valid inode stored in *result.
 
 ***		Note: lofs assumes that any filesystem returns an inode within the filesystem