Tag-based filesystems.
This commit is contained in:
parent
a10013f6a4
commit
7e20de3d0e
1 changed files with 11 additions and 1 deletions
|
@ -1141,7 +1141,7 @@ All storage devices have their own particularities, but regular hard drives and
|
|||
.FOOTNOTE2
|
||||
The rest of this section will address more
|
||||
.dq generic
|
||||
filesystems\*[*].
|
||||
filesystems\*[*] unless explicitely stated otherwise.
|
||||
.FOOTNOTE1
|
||||
Furthermore, the rich history behind filesystems is inherently related to the rich history of storage devices, this document is not supposed to be a survey on either of those.
|
||||
Let's keep it short and simple.
|
||||
|
@ -1348,6 +1348,16 @@ Finally,
|
|||
.B tmpfs
|
||||
is the more flexible one, it is used as ramfs but can be resized and only uses a necessary amount of RAM at a given point (memory is free'd once a file is removed).
|
||||
.FOOTNOTE2
|
||||
|
||||
.KS
|
||||
.B "Semantic (tag-based) filesystems" .
|
||||
Some filesystems (such as tagsistant) store data based on tags for each file which enables to index a file based on many attributes and not a single path.
|
||||
As a side effect, searching for a file in this context can be done by computing the intersection of different tags\*[*].
|
||||
.KE
|
||||
.FOOTNOTE1
|
||||
Well well well… doesn't that sound like the DODB tag triggers?
|
||||
As if databases and filesystems were intertwined somehow…
|
||||
.FOOTNOTE2
|
||||
.
|
||||
.KS
|
||||
.SSS "Conclusion on filesystems"
|
||||
|
|
Loading…
Add table
Reference in a new issue