forked from Imagelibrary/rtems
Another couple of chapters formatting under texinfo.
This commit is contained in:
@@ -8,27 +8,42 @@
|
|||||||
|
|
||||||
@chapter System Initialization
|
@chapter System Initialization
|
||||||
|
|
||||||
|
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. Mounting the base file system consists
|
||||||
|
of the following:
|
||||||
|
|
||||||
After the RTEMS initialization is performed, the application's initialization will
|
@itemize @bullet
|
||||||
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.
|
|
||||||
|
|
||||||
Mounting the base file system consists of the following:
|
@item Initialization of mount table chain control structure
|
||||||
|
|
||||||
? Initialization of mount table chain control structure
|
@item Allocation of a -jnode- structure that will server as the root node
|
||||||
? Allocation of a -jnode- structure that will server as the root node of the `In Memory
|
of the `In Memory File System'
|
||||||
File System'
|
|
||||||
? Initialization of the allocated -jnode- with the appropriate OPS, directory handlers
|
@item Initialization of the allocated -jnode- with the appropriate OPS,
|
||||||
and pathconf limits and options.
|
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
|
@item Allocation of a memory region for file system specific global
|
||||||
? Initialization of the first mount table chain entry to indicate that the mount point is
|
management variables
|
||||||
NULL and the mounted file system is the base file system
|
|
||||||
|
@item Creation of first mount table entry for the base file system
|
||||||
|
|
||||||
|
@item 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
|
||||||
|
|
||||||
|
@end itemize
|
||||||
|
|
||||||
|
|
||||||
After the base file system has been mounted, the following operations are performed
|
After the base file system has been mounted, the following operations are
|
||||||
under its directory structure:
|
performed under its directory structure:
|
||||||
|
|
||||||
? Creation of the /dev directory
|
@itemize @bullet
|
||||||
? Registration of devices under /dev directory
|
|
||||||
|
@item Creation of the /dev directory
|
||||||
|
|
||||||
|
@item Registration of devices under /dev directory
|
||||||
|
|
||||||
|
@end itemize
|
||||||
|
|
||||||
|
|||||||
@@ -8,19 +8,38 @@
|
|||||||
|
|
||||||
@chapter Pathname Evaluation
|
@chapter Pathname Evaluation
|
||||||
|
|
||||||
XXX Include graphic of the path evaluation process with Jennifer's explanations
|
XXX Include graphic of the path evaluation process with Jennifer's
|
||||||
|
explanations
|
||||||
|
|
||||||
? There are two pathname evaluation routines. The handler patheval() is called to find,
|
@itemize @bullet
|
||||||
verify privlages on and return information on a node that exists. The handler
|
|
||||||
evalformake() is called to find, verify permissions, and return information on a node
|
@item There are two pathname evaluation routines. The handler patheval()
|
||||||
that is to become a parent. Additionally, evalformake() returns a pointer to the start
|
is called to find, verify privlages on and return information on a node
|
||||||
of the name of the new node to be created.
|
that exists. The handler evalformake() is called to find, verify
|
||||||
? Pathname evaluation is specific to a file system
|
permissions, and return information on a node that is to become a parent.
|
||||||
? Mechanics of crossing a mount point during the evaluation of a path name
|
Additionally, evalformake() returns a pointer to the start of the name of
|
||||||
? Role of rtems_filesystem_location_info_t structure
|
the new node to be created.
|
||||||
? Finding file system node information
|
|
||||||
? Finding file system node handlers
|
@item Pathname evaluation is specific to a file system
|
||||||
? Finding file system node operations table
|
|
||||||
? Finding mount table entry for the file system that this node is part of
|
@item Mechanics of crossing a mount point during the evaluation of a path
|
||||||
|
name
|
||||||
|
|
||||||
|
@item Role of rtems_filesystem_location_info_t structure
|
||||||
|
|
||||||
|
@itemize @bullet
|
||||||
|
|
||||||
|
@item Finding file system node information
|
||||||
|
|
||||||
|
@item Finding file system node handlers
|
||||||
|
|
||||||
|
@item Finding file system node operations table
|
||||||
|
|
||||||
|
@item Finding mount table entry for the file system that this node is part
|
||||||
|
of
|
||||||
|
|
||||||
|
@end itemize
|
||||||
|
|
||||||
|
@end itemize
|
||||||
|
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user