--- linux-2.4.32/Documentation/Configure.help	2005-12-04 22:04:46.000000000 +0100
+++ linux-2.4.32-squashfs/Documentation/Configure.help	2005-12-05 15:51:47.000000000 +0100
@@ -18476,6 +18476,57 @@
   root partition (the one containing the directory /) cannot be a
   module, so saying M could be dangerous.  If unsure, say N.
 
+SquashFS 2.2 - Squashed file system support
+CONFIG_SQUASHFS
+  Saying Y here includes support for SquashFs 2.2 (Compressed Read-Only File
+  System).  Squashfs is a highly compressed read-only filesystem for Linux.
+  It uses zlib compression to compress both files, inodes and directories.
+  Inodes in the system are very small and all blocks are packed to minimise
+  data overhead. Block sizes greater than 4K are supported up to a maximum of 64K.
+
+  Squashfs is intended for general read-only filesystem use, for archival
+  use (i.e. in cases where a .tar.gz file may be used), and in embedded
+  systems where low overhead is needed.  Further information and filesystem tools
+  are available from http://squashfs.sourceforge.net.
+
+  If you want to compile this as a module ( = code which can be
+  inserted in and removed from the running kernel whenever you want),
+  say M here and read <file:Documentation/modules.txt>.  The module
+  will be called squashfs.  Note that the root file system (the one
+  containing the directory /) cannot be compiled as a module.
+
+  If unsure, say N.
+
+Additional options for memory-constrained systems
+CONFIG_SQUASHFS_EMBEDDED
+  Saying Y here allows you to specify cache sizes and how Squashfs
+  allocates memory.  This is only intended for memory constrained
+  systems.
+
+  If unsure, say N.
+
+Number of fragments cached
+CONFIG_SQUASHFS_FRAGMENT_CACHE_SIZE
+  By default SquashFS caches the last 3 fragments read from
+  the filesystem.  Increasing this amount may mean SquashFS
+  has to re-read fragments less often from disk, at the expense
+  of extra system memory.  Decreasing this amount will mean
+  SquashFS uses less memory at the expense of extra reads from disk.
+
+  Note there must be at least one cached fragment.  Anything
+  much more than three will probably not make much difference.
+
+Use Vmalloc rather than Kmalloc
+CONFIG_SQUASHFS_VMALLOC
+  By default SquashFS uses kmalloc to obtain fragment cache memory.
+  Kmalloc memory is the standard kernel allocator, but it can fail
+  on memory constrained systems.  Because of the way Vmalloc works,
+  Vmalloc can succeed when kmalloc fails.  Specifying this option
+  will make SquashFS always use Vmalloc to allocate the
+  fragment cache memory.
+
+  If unsure, say N.
+
 /proc file system support
 CONFIG_PROC_FS
   This is a virtual file system providing information about the status