source: rtems/doc/filesystem/preface.texi @ 7779ace

4.104.114.84.95
Last change on this file since 7779ace was df4edf29, checked in by Joel Sherrill <joel.sherrill@…>, on 10/07/99 at 22:31:00

Added Base File System chapter. Builds completely.

  • Property mode set to 100644
File size: 2.2 KB
Line 
1@c
2@c  COPYRIGHT (c) 1988-1998.
3@c  On-Line Applications Research Corporation (OAR).
4@c  All rights reserved.
5@c
6@c  $Id$
7@c
8
9@ifinfo
10@node Preface, Base File System, Top, Top
11@end ifinfo
12@unnumbered Preface
13
14The following file system capabilities have been added to the existing
15RTEMS system:
16
17@itemize @bullet
18
19@item Mountable file systems
20
21@item Hierarchical file system directory structure
22
23@item POSIX compliant set of routines for the manipulation of files and directories
24
25@item Individual file and directory support for the following:
26
27@enumerate
28
29@item Permissions for read, write and execute
30
31@item User ID
32
33@item Group ID
34
35@item Access time
36
37@item Modification time
38
39@item Creation time
40
41@end enumerate
42
43@item Hard links to files and directories are supported
44
45@item Symbolic links to files and directories are supported
46
47@end itemize
48
49These enhancements have been made to provide the framework for `UNIX like'
50file system support. The POSIX file and directory functions have been
51implemented to allow a standard method of accessing file, device and
52directory information within the file system. The file system concept that
53has been implemented allows for expansion and adaptation of the file
54system to a variety of existing and future data storage devices. To this
55end, file system mount and unmount capabilities have been included in this
56RTEMS framework.
57
58This framework slightly alters the manner in which devices are handled
59under RTEMS. Devices that are defined under a given RTEMS configuration
60will now be registered as files in a mounted file system. Access to these
61devices and their associated device handlers will be obtained through the
62traditional file system open(), read(), write(), lseek(), fstat() and
63ioctl() functions.
64
65A node structure is maintained for each file, device, and directory in the
66file system. The node structure is used to manage ownership, access
67rights, access time, modification time, and creation time. A union of
68structures within the nodal structure provide for manipulation of file
69data, device selection, or directory content as required by the nodal
70type. Manipulation of these properties is accomplished through the POSIX
71set of file and directory functions.
72
Note: See TracBrowser for help on using the repository browser.