Added initial version of 3 other chapters.

4 files changed, 49 insertions, 32 deletions

diff --git a/doc/filesystem/Makefile b/doc/filesystem/Makefile
index c2dfb0ce3a..4f112b1609 100644
--- a/doc/filesystem/Makefile
+++ b/doc/filesystem/Makefile
@@ -21,7 +21,8 @@ dirs:
 
 COMMON_FILES=../common/cpright.texi ../common/setup.texi
 
-GENERATED_FILES=basefs.texi applayering.texi
+GENERATED_FILES=basefs.texi applayering.texi patheval.texi \
+    init.texi mounting.texi 
 
 FILES= $(PROJECT).texi \
   preface.texi $(GENERATED_FILES)
@@ -61,6 +62,21 @@ applayering.texi: applayering.t Makefile
 	   -u "Top" \
 	   -n "" ${*}.t
 
+patheval.texi: patheval.t Makefile
+	$(BMENU) -p "" \
+	   -u "Top" \
+	   -n "" ${*}.t
+
+init.texi: init.t Makefile
+	$(BMENU) -p "" \
+	   -u "Top" \
+	   -n "" ${*}.t
+
+mounting.texi: mounting.t Makefile
+	$(BMENU) -p "" \
+	   -u "Top" \
+	   -n "" ${*}.t
+
 html: dirs $(FILES)
 	-mkdir -p $(WWW_INSTALL)/$(PROJECT)
 	# rm -f $(WWW_INSTALL)/$(PROJECT)/networkflow.jpg
diff --git a/doc/filesystem/filesystem.texi b/doc/filesystem/filesystem.texi
index 267789b714..b35898a8ea 100644
--- a/doc/filesystem/filesystem.texi
+++ b/doc/filesystem/filesystem.texi
@@ -65,6 +65,9 @@ END-INFO-DIR-ENTRY
 @include preface.texi
 @include basefs.texi
 @include applayering.texi
+@include patheval.texi
+@include init.texi
+@include mounting.texi
 @ifinfo
 @node Top, Preface, (dir), (dir)
 @top filesystem
@@ -75,6 +78,9 @@ This is the online version of the RTEMS Filesystem Design Guide.
 * Preface::
 * Base File System::
 * Applications and Functional Layering::
+* Pathname Evaluation::
+* System Initialization::
+* Mounting and Unmounting File Systems::
 * Command and Variable Index::
 * Concept Index::
 @end menu
diff --git a/doc/filesystem/init.t b/doc/filesystem/init.t
index e2a6f063d6..088db2aa7f 100644
--- a/doc/filesystem/init.t
+++ b/doc/filesystem/init.t
@@ -1,9 +1,15 @@
+@c
+@c  COPYRIGHT (c) 1988-1998.
+@c  On-Line Applications Research Corporation (OAR).
+@c  All rights reserved.
+@c
+@c  $Id$
+@c
 
+@chapter System Initialization
 
-System Initialization
 
-
-	After the RTEMS initialization is performed, the application's initialization will 
+After the RTEMS initialization is performed, the application's initialization will 
 be performed. Part of initialization is a call to rtems_filesystem_initialize(). This routine 
 will mount the `In Memory File System' as the base file system. 
 
diff --git a/doc/filesystem/mounting.t b/doc/filesystem/mounting.t
index 65c4da6995..64d0b79cd8 100644
--- a/doc/filesystem/mounting.t
+++ b/doc/filesystem/mounting.t
@@ -1,23 +1,12 @@
-Mounting the base file system consists of the following:
+@c
+@c  COPYRIGHT (c) 1988-1998.
+@c  On-Line Applications Research Corporation (OAR).
+@c  All rights reserved.
+@c
+@c  $Id$
+@c
 
-? Initialization of mount table chain control structure 
-? Allocation of a -jnode- structure that will server as the root node of the `In Memory 
-File System'
-? Initialization of the allocated -jnode- with the appropriate OPS, directory handlers 
-and pathconf limits and options.
-? Allocation of a memory region for file system specific global management variables
-? Creation of first mount table entry for the base file system 
-? Initialization of the first mount table chain entry to indicate that the mount point is 
-NULL and the mounted file system is the base file system
-
-
-After the base file system has been mounted, the following operations are performed 
-under its directory structure:
-
-? Creation of the /dev directory
-? Registration of devices under /dev directory 
-
-Mounting and Unmounting File Systems 
+@chapter Mounting and Unmounting File Systems 
 
 ? Characteristics of a Mount Point
 ? The mount point must be a directory. It may have files and other directories under 
@@ -31,14 +20,14 @@ point after the mount is complete.
 ? Content of the mount table chain entry
 
 struct rtems_filesystem_mount_table_entry_tt
-{
-  	Chain_Node                             			Node;
-  	rtems_filesystem_location_info_t       		mt_point_node;
-  	rtems_filesystem_location_info_t       		mt_fs_root;
-  	int                                    			options;
-  	void                                  			*fs_info;
+@{
+   Chain_Node                                Node;
+   rtems_filesystem_location_info_t         mt_point_node;
+   rtems_filesystem_location_info_t         mt_fs_root;
+   int                                       options;
+   void                                     *fs_info;
 
-  	rtems_filesystem_limits_and_options_t  	pathconf_limits_and_options;
+   rtems_filesystem_limits_and_options_t   pathconf_limits_and_options;
 
   /*
    *  When someone adds a mounted filesystem on a real device,
@@ -46,8 +35,8 @@ struct rtems_filesystem_mount_table_entry_tt
    *
    *  The best option long term for this is probably an open file descriptor.
    */
-  	char                                  			*dev;
-};
+   char                                     *dev;
+@};
 
 ? Adding entries to the chain during mount()
 When a file system is mounted, its presence and location in the file system