From 7779ace4bfd7e1a84fa897749dea791a1030f17b Mon Sep 17 00:00:00 2001 From: Joel Sherrill Date: Fri, 8 Oct 1999 18:36:08 +0000 Subject: [PATCH] Another couple of chapters formatting under texinfo. --- doc/filesystem/init.t | 49 +++++++++++++++++++++++++-------------- doc/filesystem/patheval.t | 45 ++++++++++++++++++++++++----------- 2 files changed, 64 insertions(+), 30 deletions(-) diff --git a/doc/filesystem/init.t b/doc/filesystem/init.t index 088db2aa7f..68d58ff783 100644 --- a/doc/filesystem/init.t +++ b/doc/filesystem/init.t @@ -8,27 +8,42 @@ @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 -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. +@itemize @bullet -Mounting the base file system consists of the following: +@item Initialization of mount table chain control structure -? 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 +@item Allocation of a -jnode- structure that will server as the root node +of the `In Memory File System' + +@item Initialization of the allocated -jnode- with the appropriate OPS, +directory handlers and pathconf limits and options. + +@item Allocation of a memory region for file system specific global +management variables + +@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 -under its directory structure: +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 +@itemize @bullet + +@item Creation of the /dev directory + +@item Registration of devices under /dev directory + +@end itemize diff --git a/doc/filesystem/patheval.t b/doc/filesystem/patheval.t index 34b9bcd584..c4aa6088f5 100644 --- a/doc/filesystem/patheval.t +++ b/doc/filesystem/patheval.t @@ -8,19 +8,38 @@ @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, -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 -that is to become a parent. Additionally, evalformake() returns a pointer to the start -of the name of the new node to be created. -? Pathname evaluation is specific to a file system -? Mechanics of crossing a mount point during the evaluation of a path name -? Role of rtems_filesystem_location_info_t structure -? Finding file system node information -? Finding file system node handlers -? Finding file system node operations table -? Finding mount table entry for the file system that this node is part of +@itemize @bullet + +@item There are two pathname evaluation routines. The handler patheval() +is called to find, 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 that is to become a parent. +Additionally, evalformake() returns a pointer to the start of the name of +the new node to be created. + +@item Pathname evaluation is specific to a file system + +@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