diff options
author | Yth - Arnaud <yth@ythogtha.org> | 2020-06-24 06:07:53 +0700 |
---|---|---|
committer | Willy Sudiarto Raharjo <willysr@slackbuilds.org> | 2020-06-24 06:07:53 +0700 |
commit | 3b089678a686bfa379a7604b7e5a24796c00facb (patch) | |
tree | 0682a54683955b9cded3e69c42c90d0ae0e66490 /system/unionfs-fuse/README | |
parent | 1a62dca8d7ceb7dfbabc679580076bcff1ceb2f3 (diff) |
system/unionfs-fuse: Added (unionfs filesystem).
Signed-off-by: Willy Sudiarto Raharjo <willysr@slackbuilds.org>
Diffstat (limited to 'system/unionfs-fuse/README')
-rw-r--r-- | system/unionfs-fuse/README | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/system/unionfs-fuse/README b/system/unionfs-fuse/README new file mode 100644 index 000000000000..f49b8ef95dd1 --- /dev/null +++ b/system/unionfs-fuse/README @@ -0,0 +1,12 @@ +unionfs-fuse is a unionfs filesystem implementation using fuse. +It is meant to be way more flexible than the current in-kernel unionfs solution. + +Why choose this stuff? + * The filesystem has to be mounted after the roots are mounted when using the standard module. + With unionfs-fuse, you can mount the roots later and their contents will appear seamlesly + * You get caching (provided by the underlying FUSE page cache) which speeds things up a lot for free + * Advanced features like copy-on-write and more + +Why NOT choose it? + * Compared to kernel-space solution we need lots of useless context switches which makes + kernel-only solution clear speed-winner |