This commit is contained in:
2024-08-06 17:33:59 +02:00
parent 6e1f478ce5
commit da14091106
81 changed files with 549 additions and 185 deletions

View File

@@ -2,7 +2,7 @@
![](img/zos_zstor.jpg)
presents itself as a filesystem to the ZMachine.
presents itself as a filesystem to the Zero VM.
### Benefits

View File

@@ -1,7 +1,7 @@
# Storage Primitives
- [ZOS Filesystem](zos_fs.md) : deduped immutable filesystem
- [ZOS Mount](zmount.md) : a part of a SSD (fast disk), mounted underneath your zmachine
- [ZOS Mount](zmount.md) : a part of a SSD (fast disk), mounted underneath your zero_vm
- [Quantum Safe Filesystem](qsfs.md) : unbreakable storage system (secondary storage only)
- [Zero-DB](zdb.md) : the lowest level storage primitive, is a key value stor, used underneath other storage mechanisms typically
- [Zero-Disk](zdisk.md) : OEM only, virtual disk format

View File

@@ -9,9 +9,9 @@ A deduped filesystem which is more efficient compared to images as used in other
## Uses FLIST Inside
In Zero-OS, `flist` is the format used to store zmachine images. This format is made to provide a complete mountable remote filesystem, but downloading only the files contents that you actually needs.
In Zero-OS, `flist` is the format used to store zero_vm images. This format is made to provide a complete mountable remote filesystem, but downloading only the files contents that you actually needs.
In practice, Flist itself is a small database which contains metadata about files and directories, file payload are stored on a tfgrid hub. You only need to download payload when you need it, this dramatically reduce zmachine boot time, bandwidth and disk overhead.
In practice, Flist itself is a small database which contains metadata about files and directories, file payload are stored on a tfgrid hub. You only need to download payload when you need it, this dramatically reduce zero_vm boot time, bandwidth and disk overhead.
### Why this ZFlist Concept