Changeset 7779ace in rtems


Ignore:
Timestamp:
10/08/99 18:36:08 (23 years ago)
Author:
Joel Sherrill <joel.sherrill@…>
Branches:
4.10, 4.11, 4.8, 4.9, 5, master
Children:
ee6284c
Parents:
4d771349
Message:

Another couple of chapters formatting under texinfo.

Location:
doc/filesystem
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • doc/filesystem/init.t

    r4d771349 r7779ace  
    99@chapter System Initialization
    1010
     11After the RTEMS initialization is performed, the application's
     12initialization will be performed. Part of initialization is a call to
     13rtems_filesystem_initialize(). This routine will mount the `In Memory File
     14System' as the base file system.  Mounting the base file system consists
     15of the following:
    1116
    12 After the RTEMS initialization is performed, the application's initialization will
    13 be performed. Part of initialization is a call to rtems_filesystem_initialize(). This routine
    14 will mount the `In Memory File System' as the base file system.
     17@itemize @bullet
    1518
    16 Mounting the base file system consists of the following:
     19@item Initialization of mount table chain control structure
    1720
    18 ? Initialization of mount table chain control structure
    19 ? Allocation of a -jnode- structure that will server as the root node of the `In Memory
    20 File System'
    21 ? Initialization of the allocated -jnode- with the appropriate OPS, directory handlers
    22 and pathconf limits and options.
    23 ? Allocation of a memory region for file system specific global management variables
    24 ? Creation of first mount table entry for the base file system
    25 ? Initialization of the first mount table chain entry to indicate that the mount point is
    26 NULL and the mounted file system is the base file system
     21@item Allocation of a -jnode- structure that will server as the root node
     22of the `In Memory File System'
     23
     24@item Initialization of the allocated -jnode- with the appropriate OPS,
     25directory handlers and pathconf limits and options.
     26
     27@item Allocation of a memory region for file system specific global
     28management variables
     29
     30@item Creation of first mount table entry for the base file system
     31
     32@item Initialization of the first mount table chain entry to indicate that
     33the mount point is NULL and the mounted file system is the base file
     34system
     35
     36@end itemize
    2737
    2838
    29 After the base file system has been mounted, the following operations are performed
    30 under its directory structure:
     39After the base file system has been mounted, the following operations are
     40performed under its directory structure:
    3141
    32 ? Creation of the /dev directory
    33 ? Registration of devices under /dev directory
     42@itemize @bullet
    3443
     44@item Creation of the /dev directory
     45
     46@item Registration of devices under /dev directory
     47
     48@end itemize
     49
  • doc/filesystem/patheval.t

    r4d771349 r7779ace  
    99@chapter Pathname Evaluation
    1010
    11 XXX Include graphic of the path evaluation process with Jennifer's explanations
     11XXX Include graphic of the path evaluation process with Jennifer's
     12explanations
    1213
    13 ? There are two pathname evaluation routines.  The handler patheval() is called to find,
    14 verify privlages on and return information on a node that exists.  The handler
    15 evalformake() is called to find, verify permissions, and return information on a node
    16 that is to become a parent.  Additionally, evalformake() returns a pointer to the start
    17 of the name of the new node to be created.
    18 ? Pathname evaluation is specific to a file system
    19 ? Mechanics of crossing a mount point during the evaluation of a path name
    20 ? Role of rtems_filesystem_location_info_t structure
    21 ? Finding file system node information
    22 ? Finding file system node handlers
    23 ? Finding file system node operations table
    24 ? Finding mount table entry for the file system that this node is part of
     14@itemize @bullet
     15
     16@item There are two pathname evaluation routines.  The handler patheval()
     17is called to find, verify privlages on and return information on a node
     18that exists.  The handler evalformake() is called to find, verify
     19permissions, and return information on a node that is to become a parent. 
     20Additionally, evalformake() returns a pointer to the start of the name of
     21the new node to be created.
     22
     23@item Pathname evaluation is specific to a file system
     24
     25@item Mechanics of crossing a mount point during the evaluation of a path
     26name
     27
     28@item Role of rtems_filesystem_location_info_t structure
     29
     30@itemize @bullet
     31
     32@item Finding file system node information
     33
     34@item Finding file system node handlers
     35
     36@item Finding file system node operations table
     37
     38@item Finding mount table entry for the file system that this node is part
     39of
     40
     41@end itemize
     42
     43@end itemize
    2544
    2645
Note: See TracChangeset for help on using the changeset viewer.