diff options
author | Joel Sherrill <joel.sherrill@OARcorp.com> | 1999-10-08 18:26:28 +0000 |
---|---|---|
committer | Joel Sherrill <joel.sherrill@OARcorp.com> | 1999-10-08 18:26:28 +0000 |
commit | 4d77134923d1b9b4fcea016fc2f1f700823c42db (patch) | |
tree | f87f7a8a489f603686d2853d2ebf1eb9d2310101 /doc/filesystem/mounting.t | |
parent | Renamed path_eval to patheval (diff) | |
download | rtems-4d77134923d1b9b4fcea016fc2f1f700823c42db.tar.bz2 |
Added initial version of 3 other chapters.
Diffstat (limited to '')
-rw-r--r-- | doc/filesystem/mounting.t | 45 |
1 files changed, 17 insertions, 28 deletions
diff --git a/doc/filesystem/mounting.t b/doc/filesystem/mounting.t index 65c4da6995..64d0b79cd8 100644 --- a/doc/filesystem/mounting.t +++ b/doc/filesystem/mounting.t @@ -1,23 +1,12 @@ -Mounting the base file system consists of the following: +@c +@c COPYRIGHT (c) 1988-1998. +@c On-Line Applications Research Corporation (OAR). +@c All rights reserved. +@c +@c $Id$ +@c -? 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 - - -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 - -Mounting and Unmounting File Systems +@chapter Mounting and Unmounting File Systems ? Characteristics of a Mount Point ? The mount point must be a directory. It may have files and other directories under @@ -31,14 +20,14 @@ point after the mount is complete. ? Content of the mount table chain entry struct rtems_filesystem_mount_table_entry_tt -{ - Chain_Node Node; - rtems_filesystem_location_info_t mt_point_node; - rtems_filesystem_location_info_t mt_fs_root; - int options; - void *fs_info; +@{ + Chain_Node Node; + rtems_filesystem_location_info_t mt_point_node; + rtems_filesystem_location_info_t mt_fs_root; + int options; + void *fs_info; - rtems_filesystem_limits_and_options_t pathconf_limits_and_options; + rtems_filesystem_limits_and_options_t pathconf_limits_and_options; /* * When someone adds a mounted filesystem on a real device, @@ -46,8 +35,8 @@ struct rtems_filesystem_mount_table_entry_tt * * The best option long term for this is probably an open file descriptor. */ - char *dev; -}; + char *dev; +@}; ? Adding entries to the chain during mount() When a file system is mounted, its presence and location in the file system |