Differences between version 21 and previous revision of FileSystem.
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 21 | Last edited on Monday, April 5, 2004 4:14:25 am | by AristotlePagaltzis | Revert |
| Older page: | version 19 | Last edited on Saturday, January 10, 2004 3:26:59 pm | by JohnMcPherson | Revert |
@@ -19,8 +19,8 @@
*The directory is a file that associates inodes to filenames. The kernel has no special data strcture to represent a directory, which is treated like a normal file in most situations. Functions specific to each filesystem-type are used to read and modify the contents of a directory independently of the actual layout of its data.
*The file itself is something that is associated to an inode. Usually files are data areas, but they can also be directories, devices, FIFO's or sockets. An ``open file'' is described in the Linux kernel by a struct file item; the structure encloses a pointer to the inode representing the file. file structures are created by system calls like open, pipe and socket, and are shared by father and child across fork.
-See also [Mount],
[WikiPedia:Filesystem] and
-* __Captive__: The first free [NTFS] read/write filesystem for GNU/Linux. See : http://www.jankratochvil.net/project/captive/
+See also [Mount] and
[WikiPedia:Filesystem].
+
----
CategoryBeginners
