Changeset 4d771349 in rtems for doc/filesystem


Ignore:
Timestamp:
10/08/99 18:26:28 (23 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:
4 edited

Legend:

Unmodified
Added
Removed
  • doc/filesystem/Makefile

    r0486ca5 r4d771349  
    2222COMMON_FILES=../common/cpright.texi ../common/setup.texi
    2323
    24 GENERATED_FILES=basefs.texi applayering.texi
     24GENERATED_FILES=basefs.texi applayering.texi patheval.texi \
     25    init.texi mounting.texi
    2526
    2627FILES= $(PROJECT).texi \
     
    6263           -n "" ${*}.t
    6364
     65patheval.texi: patheval.t Makefile
     66        $(BMENU) -p "" \
     67           -u "Top" \
     68           -n "" ${*}.t
     69
     70init.texi: init.t Makefile
     71        $(BMENU) -p "" \
     72           -u "Top" \
     73           -n "" ${*}.t
     74
     75mounting.texi: mounting.t Makefile
     76        $(BMENU) -p "" \
     77           -u "Top" \
     78           -n "" ${*}.t
     79
    6480html: dirs $(FILES)
    6581        -mkdir -p $(WWW_INSTALL)/$(PROJECT)
  • doc/filesystem/filesystem.texi

    r0486ca5 r4d771349  
    6666@include basefs.texi
    6767@include applayering.texi
     68@include patheval.texi
     69@include init.texi
     70@include mounting.texi
    6871@ifinfo
    6972@node Top, Preface, (dir), (dir)
     
    7679* Base File System::
    7780* Applications and Functional Layering::
     81* Pathname Evaluation::
     82* System Initialization::
     83* Mounting and Unmounting File Systems::
    7884* Command and Variable Index::
    7985* Concept Index::
  • doc/filesystem/init.t

    r0486ca5 r4d771349  
     1@c
     2@c  COPYRIGHT (c) 1988-1998.
     3@c  On-Line Applications Research Corporation (OAR).
     4@c  All rights reserved.
     5@c
     6@c  $Id$
     7@c
     8
     9@chapter System Initialization
    110
    211
    3 System Initialization
    4 
    5 
    6         After the RTEMS initialization is performed, the application's initialization will
     12After the RTEMS initialization is performed, the application's initialization will
    713be performed. Part of initialization is a call to rtems_filesystem_initialize(). This routine
    814will mount the `In Memory File System' as the base file system.
  • doc/filesystem/mounting.t

    r0486ca5 r4d771349  
    1 Mounting the base file system consists of the following:
     1@c
     2@c  COPYRIGHT (c) 1988-1998.
     3@c  On-Line Applications Research Corporation (OAR).
     4@c  All rights reserved.
     5@c
     6@c  $Id$
     7@c
    28
    3 ? Initialization of mount table chain control structure
    4 ? Allocation of a -jnode- structure that will server as the root node of the `In Memory
    5 File System'
    6 ? Initialization of the allocated -jnode- with the appropriate OPS, directory handlers
    7 and pathconf limits and options.
    8 ? Allocation of a memory region for file system specific global management variables
    9 ? Creation of first mount table entry for the base file system
    10 ? Initialization of the first mount table chain entry to indicate that the mount point is
    11 NULL and the mounted file system is the base file system
    12 
    13 
    14 After the base file system has been mounted, the following operations are performed
    15 under its directory structure:
    16 
    17 ? Creation of the /dev directory
    18 ? Registration of devices under /dev directory
    19 
    20 Mounting and Unmounting File Systems
     9@chapter Mounting and Unmounting File Systems
    2110
    2211? Characteristics of a Mount Point
     
    3221
    3322struct rtems_filesystem_mount_table_entry_tt
    34 {
    35         Chain_Node                                              Node;
    36         rtems_filesystem_location_info_t                mt_point_node;
    37         rtems_filesystem_location_info_t                mt_fs_root;
    38         int                                                     options;
    39         void                                                    *fs_info;
     23@{
     24   Chain_Node                                Node;
     25   rtems_filesystem_location_info_t         mt_point_node;
     26   rtems_filesystem_location_info_t         mt_fs_root;
     27   int                                       options;
     28   void                                     *fs_info;
    4029
    41         rtems_filesystem_limits_and_options_t   pathconf_limits_and_options;
     30   rtems_filesystem_limits_and_options_t   pathconf_limits_and_options;
    4231
    4332  /*
     
    4736   *  The best option long term for this is probably an open file descriptor.
    4837   */
    49         char                                                    *dev;
    50 };
     38   char                                     *dev;
     39@};
    5140
    5241? Adding entries to the chain during mount()
Note: See TracChangeset for help on using the changeset viewer.