mirror of
https://github.com/Ponce/slackbuilds
synced 2024-11-06 08:26:50 +01:00
9962637b97
Signed-off-by: B. Watson <yalhcru@gmail.com> Signed-off-by: Willy Sudiarto Raharjo <willysr@slackbuilds.org> |
||
---|---|---|
.. | ||
README | ||
slack-desc | ||
unionfs-fuse.info | ||
unionfs-fuse.SlackBuild |
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 a kernel-only solution clear speed-winner.