Changes between Version 2 and Version 3 of file_system
- Timestamp:
- Jan 11, 2020, 9:21:42 PM (3 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
file_system
v2 v3 7 7 As most POSIX compliant operating systems, ALMOS-MKH sees the external storage device as an array of clusters, where each clusters can store one page of 4 Kbytes. Each cluster occupies eight 512 bytes physical sectors, and is indexed by a cluster identifier, calledd ''cluster_id''. 8 8 9 To support various File System types, ALMOS-MKH defines a generic Virtual File System API defined in the 10 [https://www-soc.lip6.fr/trac/almos-mkh/browser/trunk/kernel/fs/vfs.c almos-mkh/kernel/fs/vfs.c] et [https://www-soc.lip6.fr/trac/almos-mkh/browser/trunk/kernel/fs/vfs.h almos-mkh/kernel/fs/vfs.h] files. 9 To support various File System types, ALMOS-MKH defines a generic Virtual File System API defined in the [https://www-soc.lip6.fr/trac/almos-mkh/browser/trunk/kernel/fs/vfs.c almos-mkh/kernel/fs/vfs.c], and [https://www-soc.lip6.fr/trac/almos-mkh/browser/trunk/kernel/fs/vfs.h almos-mkh/kernel/fs/vfs.h] files. 11 10 12 11 All supported fille systems are supposed to have a hierarchical tree_based structure, where some special ''directory'' files contain ''links'' to other files that can be ''directory'' files, or ''terminal'' files. Therefore, any file X in the file system can be unambiguously defined by a ''pathname'' describing the path from the VFS root to the X file. A ''directory'' file has only on single path name, but a ''terminal'' file can have several ''parent'' directories, defining several path names for one single file.