| |||||||||||||
Unioning file systems: Architecture, features, and design choicesUnioning file systems: Architecture, features, and design choicesPosted Jan 16, 2013 0:00 UTC (Wed) by hummassa (subscriber, #307)In reply to: Unioning file systems: Architecture, features, and design choices by anselm Parent article: Unioning file systems: Architecture, features, and design choices
You can have "negative filesystem skeletons" like you have in some unionfs implementations. That way, you do "/x -> /a:-/b:/c:-/d" and if you remove a file in /x, the implementation will touch the same name (modulo an extension or prefix) under /b, that will mark said file as inexistent even if it exists in /c...
(Log in to post comments)
|
|||||||||||||