1 <!-- Copyright (C) 2003 Red Hat, Inc. -->
2 <!-- This material may be distributed only subject to the terms -->
3 <!-- and conditions set forth in the Open Publication License, v1.0 -->
4 <!-- or later (the latest version is presently available at -->
5 <!-- http://www.opencontent.org/openpub/). -->
6 <!-- Distribution of the work or derivative of the work in any -->
7 <!-- standard (paper) book form is prohibited unless prior -->
8 <!-- permission is obtained from the copyright holder. -->
13 ><meta name="MSSmartTagsPreventParsing" content="TRUE">
16 CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
19 TITLE="eCos Reference Manual"
20 HREF="ecos-ref.html"><LINK
22 TITLE="File System Support Infrastructure"
23 HREF="fileio.html"><LINK
25 TITLE="File System Support Infrastructure"
26 HREF="fileio.html"><LINK
28 TITLE="File System Table"
29 HREF="fileio-fstab.html"></HEAD
40 SUMMARY="Header navigation table"
49 >eCos Reference Manual</TH
71 HREF="fileio-fstab.html"
84 NAME="FILEIO-INTRO">Chapter 19. Introduction</H1
86 >This document describes the filesystem infrastructure provided in
87 eCos. This is implemented by the FILEIO package and provides POSIX
88 compliant file and IO operations together with the BSD socket
89 API. These APIs are described in the relevant standards and original
90 documentation and will not be described here. See <A
91 HREF="posix-standard-support.html"
93 > for details of which parts of the
94 POSIX standard are supported.</P
96 >This document is concerned with the interfaces presented to client
97 filesystems and network protocol stacks.</P
99 >The FILEIO infrastructure consist mainly of a set of tables containing
100 pointers to the primary interface functions of a file system. This
101 approach avoids problems of namespace pollution (for example several
102 filesystems can have a function called <TT
105 >, so long as they are
106 static). The system is also structured to eliminate the need for
107 dynamic memory allocation.</P
109 >New filesystems can be written directly to the interfaces described
110 here. Existing filesystems can be ported very easily by the
111 introduction of a thin veneer porting layer that translates FILEIO
112 calls into native filesystem calls. </P
114 >The term filesystem should be read fairly loosely in this
115 document. Object accessed through these interfaces could equally be
116 network protocol sockets, device drivers, fifos, message queues or any
117 other object that can present a file-like interface.</P
124 SUMMARY="Footer navigation table"
153 HREF="fileio-fstab.html"
163 >File System Support Infrastructure</TD
177 >File System Table</TD