Changeset 4d771349 in rtems

Timestamp:

10/08/99 18:26:28 (24 years ago)

Author:

Joel Sherrill <joel.sherrill@…>

Branches:

4.10, 4.11, 4.8, 4.9, 5, master

Children:

7779ace

Parents:

0486ca5

Message:

Added initial version of 3 other chapters.

Location:

doc/filesystem

Files:

• Makefile (modified) (2 diffs)
• filesystem.texi (modified) (2 diffs)
• init.t (modified) (1 diff)
• mounting.t (modified) (3 diffs)

doc/filesystem/Makefile

@@ -22 +22 @@
 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 \
@@ -62 +63 @@
            -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)

doc/filesystem/filesystem.texi

@@ -66 +66 @@
 @include basefs.texi
 @include applayering.texi
+@include patheval.texi
+@include init.texi
+@include mounting.texi
 @ifinfo
 @node Top, Preface, (dir), (dir)
@@ -76 +79 @@
 * Base File System::
 * Applications and Functional Layering::
+* Pathname Evaluation::
+* System Initialization::
+* Mounting and Unmounting File Systems::
 * Command and Variable Index::
 * Concept Index::

doc/filesystem/init.t

@@ +1 @@
+@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. 

doc/filesystem/mounting.t

@@ -1 @@
-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
@@ -32 +21 @@
 
 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;
 
   /*
@@ -47 +36 @@
    *  The best option long term for this is probably an open file descriptor.
    */
-        char                                                    *dev;
-};
+   char                                     *dev;
+@};
 
 ? Adding entries to the chain during mount()