[Fscat-commits] jlbec commits r68 - trunk/documentation

[svn-commits at oss.oracle.com]

Author: jlbec
Date: 2007-09-04 12:00:03 -0700 (Tue, 04 Sep 2007)
New Revision: 68

Modified:
   trunk/documentation/fscat_driver.txt
Log:
Some spelling corrections

Modified: trunk/documentation/fscat_driver.txt
===================================================================
--- trunk/documentation/fscat_driver.txt	2005-08-03 03:09:48 UTC (rev 67)
+++ trunk/documentation/fscat_driver.txt	2007-09-04 19:00:03 UTC (rev 68)
@@ -37,7 +37,7 @@
 option selects dump mode.  The '-0' (zero) option changes the filename
 terminator from '\n' to '\0'.  This behavior is like "find -print0" and
 "xargs -0", allowing fully capable filenames.  The fscat(8) utility 
-lways calls the driver with the '-0' option.  Finally, the '-n' option
+always calls the driver with the '-0' option.  Finally, the '-n' option
 tells dump mode to 'not' dump.  That is, it will skip file contents.
 This is used for a detailed listing of the filesystem by fsls(8).
 
@@ -52,10 +52,10 @@
 <inode_number><space><relative_path_string><separator>
 
 The inode number is a base-10 number that can be used to retrieve the
-inode later.  How the filesystem creates and interperets this number is
+inode later.  How the filesystem creates and interprets this number is
 up to the driver.  The space is a single space.  The relative path is
 the path from the root of the filesystem to the actual object, without a
-leading '/'.  Finally, the seperator is '\n' by default or '\0' if the
+leading '/'.  Finally, the separator is '\n' by default or '\0' if the
 '-0' option was specified.  For example, a kernel tree in the root of a
 filesystem might look like:
 
@@ -71,13 +71,13 @@
 
 Dump mode takes the output of list mode as its input.  It will expect
 the input to have '\n' as the separator unless the '-0' option was
-specified.  If '-0' was specified, it will expext the input to be
+specified.  If '-0' was specified, it will expect the input to be
 separated by '\0'.
 
 This input may have been modified by a filter script.  Note that the
 driver will not do anything with the filenames it is passed.  They are
 merely passed on unchanged to the archiver.  So a filter program could
-substitute or eliminiate filenames before letting the driver dump the
+substitute or eliminate filenames before letting the driver dump the
 inodes.
 
 [Dump Mode Output Format]
@@ -95,7 +95,7 @@
 
 <headername><colon><space><value><newline>
 
-This is a pretty flexible format, but fscat does not allow permuation.
+This is a pretty flexible format, but fscat does not allow permutation.
 That is, each header field must come in correct order, or the dump is
 corrupted.  This allows good checking of consistency.  The header fields
 are as follows.
@@ -108,10 +108,10 @@
 This signifies a fscat data stream.  The second valid magic number is
 "FSCAT101".  This signifies a data stream without file contents,
 produced by a driver with the '-n' option.  fsls(8) uses this output to
-provide a detaild file listing.  Any other value means that the record
+provide a detailed file listing.  Any other value means that the record
 is invalid.  Filesystem drivers that allow a debug mode to print
 non-valid records can use the magic string "FSCAT000" (also padded) to
-prevent the archiver from trying correctly interperate the ouput.
+prevent the archiver from trying correctly interpret the output.
 
 inode: <inode_number>
 
@@ -186,7 +186,7 @@
 Unless in list ('-n') mode, after the header comes the file data, raw,
 up to <size_in_bytes> length.  Symbolic links are stored as file data,
 exactly <size_in_bytes> length.  Devices are stored in major,minor
-format.  Each number is an 8 character zero-padded hexidecimal value,
+format.  Each number is an 8 character zero-padded hexadecimal value,
 terminated by a newline.  That is "%08X\n%08X\n".  Directories, FIFOS,
 and other special files do not have any file data.  The archiver will
 see the file type in the mode and will ignore <size_in_bytes>.