Ferret File System: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 7: | Line 7: | ||
For nearer-term practical purposes, though, since I don't yet know how to roll my own filesystem :D, it looks possible to implement most of the utility of this concept as a userland application. | For nearer-term practical purposes, though, since I don't yet know how to roll my own filesystem :D, it looks possible to implement most of the utility of this concept as a userland application. | ||
==Pages== | ==Pages== | ||
* [[/design]]: | * [[/concept]]: conceptual design (for the ''big'' concept) | ||
* [[/app]]: as a userland application | * [[/design]]: technical bits | ||
* [[/app]]: as a userland application (the ''small'' concept) | |||
==Archives== | ==Archives== | ||
* [[/v0.1]] aka FileFerret: an earlier iteration of the idea, with some code | * [[/v0.1]] aka FileFerret: an earlier iteration of the idea, with some code | ||
Latest revision as of 21:57, 7 July 2024
|
FFS: why doesn't this already exist?
|
Overview
Ferret File System (FFS) is actually two ideas which can work together or separately: storage agnosticism and file format agnosticism.
Ideally it should probably be implemented as a layer between {a very simplified node-file system (files have no names, folders, or meta, just volume-unique IDs) plus volume-database} and {a filesystem API} which would be compatible with most modern software but with additional features.
For nearer-term practical purposes, though, since I don't yet know how to roll my own filesystem :D, it looks possible to implement most of the utility of this concept as a userland application.
Pages
- /concept: conceptual design (for the big concept)
- /design: technical bits
- /app: as a userland application (the small concept)
Archives
- /v0.1 aka FileFerret: an earlier iteration of the idea, with some code