diff options
Diffstat (limited to 'filesystem/system_init.rst')
| -rw-r--r-- | filesystem/system_init.rst | 76 |
1 files changed, 36 insertions, 40 deletions
diff --git a/filesystem/system_init.rst b/filesystem/system_init.rst index 4e7aab1..541ab66 100644 --- a/filesystem/system_init.rst +++ b/filesystem/system_init.rst @@ -1,30 +1,33 @@ .. comment SPDX-License-Identifier: CC-BY-SA-4.0 +.. COMMENT: COPYRIGHT (c) 1988-2002. +.. COMMENT: On-Line Applications Research Corporation (OAR). +.. COMMENT: All rights reserved. + 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 filesystem. Mounting the base filesystem 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 filesystem. Mounting the base filesystem consists of the +following: - Initialization of mount table chain control structure -- Allocation of a ``jnode`` structure that will server as the root node - of the 'In Memory Filesystem' +- Allocation of a ``jnode`` structure that will server as the root node of the + 'In Memory Filesystem' -- Initialization of the allocated ``jnode`` with the appropriate OPS, - directory handlers and pathconf limits and options. +- Initialization of the allocated ``jnode`` with the appropriate OPS, directory + handlers and pathconf limits and options. -- Allocation of a memory region for filesystem specific global - management variables +- Allocation of a memory region for filesystem specific global management + variables - Creation of first mount table entry for the base filesystem -- Initialization of the first mount table chain entry to indicate that - the mount point is NULL and the mounted filesystem is the base file - system +- Initialization of the first mount table chain entry to indicate that the + mount point is NULL and the mounted filesystem is the base file system After the base filesystem has been mounted, the following operations are performed under its directory structure: @@ -38,10 +41,11 @@ Base Filesystem RTEMS initially mounts a RAM based file system known as the base file system. The root directory of this file system tree serves as the logical root of the -directory hierarchy (Figure 3). Under the root directory a '/dev' directory -is created under which all I/O device directories and files are registered as -part of the file system hierarchy. -.. code:: c +directory hierarchy (Figure 3). Under the root directory a '/dev' directory is +created under which all I/O device directories and files are registered as part +of the file system hierarchy. + +.. code-block:: shell Figure of the tree structure goes here. @@ -65,37 +69,29 @@ Base Filesystem Mounting At present, the first file system to be mounted is the 'In Memory File System'. It is mounted using a standard MOUNT() command in which the mount -point is NULL. This flags the mount as the first file system to be -registered under the operating system and appropriate initialization of file -system management information is performed (See figures 4 and 5). If a -different file system type is desired as the base file system, alterations -must be made to base_fs.c. This routine handles the mount of the base file -system. +point is NULL. This flags the mount as the first file system to be registered +under the operating system and appropriate initialization of file system +management information is performed (See figures 4 and 5). If a different file +system type is desired as the base file system, alterations must be made to +base_fs.c. This routine handles the mount of the base file system. -.. code:: c +.. code-block:: shell Figure of the mount table chain goes here. Once the root of the base file system has been established and it has been recorded as the mount point of the base file system, devices are integrated -into the base file system. For every device that is configured into the -system (See ioman.c) a device registration process is performed. Device -registration produces a unique dev_t handle that consists of a major and -minor device number. In addition, the configuration information for each -device contains a text string that represents the fully qualified pathname to -that device's place in the base file system's hierarchy. A file system node -is created for the device along the specified registration path. +into the base file system. For every device that is configured into the system +(See ioman.c) a device registration process is performed. Device registration +produces a unique dev_t handle that consists of a major and minor device +number. In addition, the configuration information for each device contains a +text string that represents the fully qualified pathname to that device's place +in the base file system's hierarchy. A file system node is created for the +device along the specified registration path. -.. code:: c +.. code-block:: shell Figure of the Mount Table Processing goes here. Note: Other file systems can be mounted but they are mounted onto points (directory mount points) in the base file system. - -.. COMMENT: COPYRIGHT (c) 1988-2002. - -.. COMMENT: On-Line Applications Research Corporation (OAR). - -.. COMMENT: All rights reserved. - |