@@ -61,14 +61,28 @@
    3. Differing HTTP semantics (CFLAGS, -DFILED_NONBLOCK_HTTP=1)
 	It is possible that some HTTP clients may not process the HTTP stream
 	being delivered if they cannot write to the HTTP stream itself.  This
 	has not been observed yet, but it is possible.  If these semantics are
 	needed (and they should not be) then they can be enabled with this
-	flag at the cost of performance
+	flag at the cost of performance.
+
+   4. Differing chroot() semantics (CFLAGS, -DFILED_FAKE_CHROOT=1)
+        In some cases it is desirable to mangle paths with a path prefix
+        rather than call chroot() at startup.  This is less secure and slower
+        and should be generally avoided -- however it may be necessary to do.
+        In these cases the executable may be compiled with the
+        FILED_FAKE_CHROOT C preprocessor macro defined and instead of calling
+        chroot() all HTTP requests will have the root suffix specified as the
+        argument to the "-r" or "--root" option prepended to them.
+
+   5. Differing "index.html" handling (CFLAGS, -DFILED_DONT_REDIRECT_DIRECTORIES=1)
+        Normally "filed" redirects users who request a directory to the
+        index.html file in that directory so that no memory allocations are
+        required;  This option lets the server generate the new path.
 
-   4. MIME Types (MIMETYPES)
-	For single-file convience "filed" compiles the mapping of file
+   6. MIME Types (MIMETYPES)
+	For single-file convenience "filed" compiles the mapping of file
 	extensions (the string in the filename following its last dot ("."))
 	into the executable.  This mapping comes from a file in the format of
 		type1   type1_extension1 type1_extension2...
 		type2   type2_extension1 type2_extension2...
 		...
@@ -78,11 +92,11 @@
 	mapping is desired, "/dev/null" may be specified.
 
 Log Files
 ---------
 Because "filed" relies on chroot(2) and setuid(2), log files cannot reliably
-be re-opened.  If you need log rotation a second process, which can close and
-re-open log files, must be used.  Any process may be used for writing logs to
-but if the process does not support log rotation it will not provide that
+be re-opened.  If you need log rotation then a second process, which can close
+and re-open log files, must be used.  Any process may be used for writing logs
+but if the process does not support log rotation then it will not provide that
 benefit.  For example, if you wish to write logs to syslogd(8) you can use
 logger(1), such as:
 	# ./filed --root /www --user nobody --log '|logger -t filed' --daemon