Difference between revisions of "File systems"
From Organic Design wiki
(add fuse for peerix) |
m (Caretaker: headings) |
||
| Line 3: | Line 3: | ||
It's important that the OS is able to read and write all common file systems. | It's important that the OS is able to read and write all common file systems. | ||
| − | + | ||
| + | = NTFS = | ||
Because it is based on Linux most file systems are natively supported, with the exception of NTFS. | Because it is based on Linux most file systems are natively supported, with the exception of NTFS. | ||
| Line 9: | Line 10: | ||
*[http://www.jankratochvil.net/project/captive/ Captive home page] | *[http://www.jankratochvil.net/project/captive/ Captive home page] | ||
| − | + | = Fuse = | |
User-space implementation of a filesystem API. | User-space implementation of a filesystem API. | ||
*Requires kernel module | *Requires kernel module | ||
*Good examples of custom implementation | *Good examples of custom implementation | ||
**See [[fs.c]] | **See [[fs.c]] | ||
Revision as of 20:44, 12 November 2006
|
It's important that the OS is able to read and write all common file systems.
NTFS
Because it is based on Linux most file systems are natively supported, with the exception of NTFS.
There is a utilty called Captive that can provide a read/write NTFS file system layer that will integrate with the OS in the normal way.
Fuse
User-space implementation of a filesystem API.
- Requires kernel module
- Good examples of custom implementation
- See fs.c
