Difference between revisions of "File systems"
From Organic Design wiki
(update) |
m |
||
| Line 1: | Line 1: | ||
[[Category:peerix]] | [[Category:peerix]] | ||
| − | The [[:Kernel]] requires a filesystem to start up. In unix terms this means it's ''/sbin/init'' or ''/linuxrc''. It's also important that the OS is able to read and write all common file systems. | + | The [[:Category:Kernel|Kernel]] requires a filesystem to start up. In unix terms this means it's ''/sbin/init'' or ''/linuxrc''. It's also important that the OS is able to read and write all common file systems. |
= FUSE = | = FUSE = | ||
| Line 10: | Line 10: | ||
= NTFS = | = NTFS = | ||
libntfs uses FUSE to impelment a file system wrapper for NTFS | libntfs uses FUSE to impelment a file system wrapper for NTFS | ||
| + | *see [[Virtual file systems]] | ||
Revision as of 02:43, 22 December 2006
The Kernel requires a filesystem to start up. In unix terms this means it's /sbin/init or /linuxrc. It's also important that the OS is able to read and write all common file systems.
FUSE
User-space implementation of a filesystem API.
- Requires kernel module that is standard in 2.6 kernels
- Good examples of custom implementation
- See fs.c
NTFS
libntfs uses FUSE to impelment a file system wrapper for NTFS
